trwd

Q: Boot Camp Update ver 6 fails

I recently updated my MBP 9,1 to El Capitan. So far, so good!

 

Now I'd like to upgrade my Windows 8.1 Boot Camp partition to Windows 10, so in preparation for that I decided to update Boot Camp's Windows support software. Here's Apple's page about preparing and installing the updates.

 

It keeps failing.  After almost a minute of "enumerating" messages and brief screen glitches the first hint that something's wrong is this "Windows Installer" error appears.

 

BC_error_1.PNG

 

Clicking "Close the program" seems to do nothing but then suddenly this error message appears.

 

BC_error_2.PNG

 

What's baffling is that the path shown above does actually exist, and the BootCamp.MSI file is present. I don't know if this is relevant but when I looked at BootCamp.MSIs Properties > Details tab the Comments field says "Boot Camp 5.1.5621", which doesn't match "5.0.5033" in the path. (Also note that when I checked the language setting in the registry entry for Boot Camp Services one of the keys is "DisplayVersion" with a value of 5.1.5621. Hmm)

 

Searching the interwebs for key words in the above error message yields just a few fairly old forum threads. The solutions boil down to ensuring that no other video drivers or mirror drivers should exist (examples usually cited were GotomyPC, VNC, etc.), or that Boot Camp's language setting could be wrong in the registry. The latter was easy to check and rule out. The video driver thing I addressed by uninstalling every program on my system that could in any way be using a mirror driver. I did indeed have Air Display installed, so I figured its uninstallation and removal from Device Manager fixed the problem.

 

Nope.  Got the same errors.

 

So here's the next message that appears after clicking Cancel in the above message.

 

BC_error_3.PNG

 

It seems substantive but I can't figure out how to react to it. I click the OK button the following message appears.

 

BC_error_4.PNG

 

Closing that spawns the Boot Camp update screen saying that the installation was successful.  Wrong!

 

Any suggestions?

Posted on Jul 30, 2016 9:53 PM

Close

Q: Boot Camp Update ver 6 fails

  • All replies
  • Helpful answers

Previous Page 2
  • by trwd,

    trwd trwd Aug 31, 2016 2:25 PM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 31, 2016 2:25 PM in response to Loner T

    Just out of curiosity I looked through the Bootcamp XML file on the USB stick -- even though I know next to nothing about XML. It looks to me like it is akin to a script used by the installer. Is that in any way right?

     

    In sections where "Realtek" appears I see INF files beginning with "HDA...". When I search the Drivers folder on the Bootcamp USB stick for occurrences of "HDA*" the only matches are NVidia HD audio drivers.

     

    Besides that probably useless observation, if this XML file is indeed a script is there any way to add breakpoints or pauses so I can figure out where the Windows Installer failure occurs?

     

    Just totally guessing in the dark here.

  • by Loner T,

    Loner T Loner T Aug 31, 2016 2:50 PM in response to trwd
    Level 7 (23,493 points)
    Safari
    Aug 31, 2016 2:50 PM in response to trwd

    trwd wrote:

     

    What is the significance of your statement, "$WinPEDriver$ is critical during boot/installation."? I am updating drivers for an existing installation of W10 so why bother with what appears to be a folder containing Windows PE-related drivers, or do I misunderstand your point?

    You are correct $WinPEDriver$ is useful only during pre-boot when a new installation is in progress. For example setting up BT keyboards, GPUs, etc., .

     

     

    Since it appears my only option is to manually install drivers, what's the most accurate way to determine what drivers need updating?

     

    Any tips on the order in which I should manually install drivers?

     

    Aren't I solely interested in drivers that are in the D:\BootCamp\Drivers of the USB stick?

    The most logical way is to use your Device Manager, and pick the drivers from your devices and install them. Keyboard, Mouse, Camera and Apple-specific peripherals come from the Apple folder. You only need the drivers from the Bootcamp folder. This is why normally setup.exe from the Bootcamp folder is run.

     

    You've referred to a Realtek driver a few times as being the culprit. A search of the USB stick shows NO Realtek drivers. ??

     

    I  talked with a fellow today who had an identical sounding problem updating drivers after upgrading to Win 10.  I believe his MBP is the same model as mine (Apple MacBook Pro "Core i7" 2.3 15" Mid-2012 Specs, Identifiers: Mid-2012 15" - MD103LL/A - MacBookPro9,1 - A1286 - 2556*). He said he opened Task Manager before running Apple Software Update, watched for when Realtek setup was running and killed the task. This avoided a failed update.  I tried this but the Windows Installer error message appeared while Setup was still "enumerating". No driver installers appeared in Task Manager's list of running applications. Between that and there being no apparent Realtek driver on my USB stick, I feel like I may be barking up the wrong tree.

    If you do not have RealTek drivers, then you do not need to be concerned with this part.

  • by trwd,

    trwd trwd Aug 31, 2016 2:57 PM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 31, 2016 2:57 PM in response to Loner T

    Thanks. Any comment about the XML file (my post just after the one you replied to)?

  • by Loner T,

    Loner T Loner T Aug 31, 2016 3:31 PM in response to trwd
    Level 7 (23,493 points)
    Safari
    Aug 31, 2016 3:31 PM in response to trwd

    trwd wrote:

     

    Any comment about the XML file (my post just after the one you replied to)?

    The XML is metadata for the Bootcamp.msi and setup.exe to use. If you look at AutoUnattend.xml, it is read by the WinPE setup process and it has some scripting directives. For example, see the FOR loop.

     

    <settings pass="specialize">

            <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <RunSynchronous>

                    <RunSynchronousCommand wcm:action="add">

                        <Order>1</Order>

                        <Path>cmd /c "FOR %i IN (X F E D C) DO (FOR /F "tokens=6" %t in ('vol %i:') do (IF /I %t NEQ "" (IF EXIST %i:\BootCamp\BootCamp.xml Reg ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v AppsRoot /t REG_SZ /d %i /f )))"</Path>

                    </RunSynchronousCommand>

                </RunSynchronous>

            </component>

        </settings>

  • by trwd,

    trwd trwd Aug 31, 2016 4:03 PM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 31, 2016 4:03 PM in response to Loner T

    Could the XML file be edited for debugging purposes so I could see at what point the Windows Installer fails?

  • by Loner T,Solvedanswer

    Loner T Loner T Aug 31, 2016 4:30 PM in response to trwd
    Level 7 (23,493 points)
    Safari
    Aug 31, 2016 4:30 PM in response to trwd

    This is the closest that you can come to such debugging. You can set the highlighted value to 'true' (without quotes). But this is not the same as looking at the logs of the individual drivers. This setup.exe is the one in D:\Bootcamp\. It can still do things which Apple may have chosen to suppress.

     

       <settings pass="oobeSystem">

            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <FirstLogonCommands>

                  <SynchronousCommand wcm:action="add">

                      <Description>BootCamp setup</Description>

                      <CommandLine>%AppsRoot%:\BootCamp\setup.exe</CommandLine>

                      <Order>1</Order>

                      <RequiresUserInput>false</RequiresUserInput>

                  </SynchronousCommand>

                </FirstLogonCommands>

            </component>

        </settings>

     

    If you choose this path, you make a video of it, and later play it at a slower speed (frame-by-frame, if necessary) to see if there are useful messages.

     

    What is your chosen computer language when you installed/upgraded to W10? I have seen blank error messages when anything other than US English is chosen, because there may not be an equivalent error translation in a different language.

     

    Please also see this older discussion - Solution for Bootcamp 6 error on Windows 10 .

  • by trwd,

    trwd trwd Aug 31, 2016 10:15 PM in response to trwd
    Level 1 (15 points)
    Windows Software
    Aug 31, 2016 10:15 PM in response to trwd

    Ten minutes of dog-like groveling, bowing and scraping in thanks to Loner T for his tireless and patient help here. Ironically, the solution was in the last sentence of his last reply, which included a link to another post in this forum.  For reference, here's my response to that thread after successfully updating the BC drivers to v6.

  • by Loner T,

    Loner T Loner T Sep 1, 2016 4:05 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Sep 1, 2016 4:05 AM in response to trwd

    Excellent.

  • by trwd,

    trwd trwd Sep 6, 2016 8:26 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Sep 6, 2016 8:26 AM in response to Loner T

    Ack!  Loner T, the BC6 update is back.  Is this an update to the already installed update or a redundant and invalid notification?  Could it be related to the registry edit?

     

    upgrade notice.gif

  • by Loner T,

    Loner T Loner T Sep 6, 2016 9:00 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 9:00 AM in response to trwd

    Create a Windows System Restore point, and then apply it. It looks like the first 6.0 update.

  • by trwd,

    trwd trwd Sep 6, 2016 9:13 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Sep 6, 2016 9:13 AM in response to Loner T

    That's the one I finally successfully installed a few days ago, detailed in this thread. Why reinstall it?

  • by Loner T,

    Loner T Loner T Sep 6, 2016 9:28 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Sep 6, 2016 9:28 AM in response to trwd

    If it is already installed, it will just check and skip. A Restore point is for safety.

Previous Page 2