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

Page 1 Next
  • by Loner T,

    Loner T Loner T Jul 31, 2016 5:25 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Jul 31, 2016 5:25 AM in response to trwd

    On Install Windows 7 and earlier on your Mac using Boot Camp - Apple Support, the drivers for your Mac year/model to a USB Flash drive. .5621 seems to correct version. Switch to Windows and run setup.exe and check if your update finishes. If Windows was installed with proper BC drivers, it should already be in place.

     

    If you already have .5621 already downloaded, check Bootcamp.xml for the version of Bootcamp.msi specific to your Mac. I will also check in my BC drivers repository.

  • by trwd,

    trwd trwd Jul 31, 2016 6:50 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Jul 31, 2016 6:50 AM in response to Loner T

    Thank you very much for replying, LonerT. You're a wonderful resource to this community.

     

    In your reply you refer to an old article applicable to Windows 7 and earlier. Are you saying that the version number "5.1.5621" I found in a couple places indicates that I must have used that version during my original install of Boot Camp? Being that this MBP is several years old, that could be the case.

     

    But I do not understand how to react to the next part of your reply:

     

    "Switch to Windows and run setup.exe and check if your update finishes. If Windows was installed with proper BC drivers, it should already be in place."

     

    The sequence of error events in my original post are from running the latest setup.exe in Windows. Are you implying that I should find and try installing the old 5.1.5621 Boot Camp? If so, where can I find it?

     

    Any idea why the path the new setup errors out at is: C:\ProgramData\Apple\Installer Cache\Boot Camp 5.0.5033 ?

     

    I looked at the XML file in the new Boot Camp flash drive (where the new setup.exe resides). There are a lot of version number cited:

    <ProductVersion>6.0.6136

    <FileVersion>5.1.5.0

    and others

     

    My uninformed gut reaction to this problem is that the new setup.exe is detecting a mismatch between the Boot Camp version currently installed and references to it in the Registry. But that's just a guess.  The Windows Installer crash suggests a bug in their code (an inability to properly handle this situation).

     

    Could I edit the new XML file to ignore or deal with the version mismatch, if indeed that's the problem?

     

    I will greatly appreciate it if you can give me a little more direction as to what to do next to troubleshoot or fix this problem. Thanks!

  • by Loner T,

    Loner T Loner T Jul 31, 2016 7:14 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Jul 31, 2016 7:14 AM in response to trwd

    trwd wrote:

     

    In your reply you refer to an old article applicable to Windows 7 and earlier. Are you saying that the version number "5.1.5621" I found in a couple places indicates that I must have used that version during my original install of Boot Camp? Being that this MBP is several years old, that could be the case.

    From Boot Camp Support Software 5.1.5621,

     

    File Size: 924.9 MB

    System Requirements

    • MacBook Air (11-inch & 13-inch, Mid 2011)
    • MacBook Air (11-inch & 13-inch, Mid 2012)
    • MacBook Pro (15-inch & 17-inch, Mid 2010)
    • MacBook Pro (13-inch, & 15-inch, Early 2011)
    • MacBook Pro (17-inch, Early 2011)
    • MacBook Pro (13-inch,15-inch & 17-inch  Late 2011)
    • MacBook Pro (13-inch & 15-inch, Mid 2012)
    • MacBook Pro (Retina, Mid 2012)
    • MacBook Pro (Retina, 13-inch, Late 2012)
    • MacBook Pro (Retina, 13-inch and 15-inch, Early 2013)
    • Mac Pro (Early 2009)
    • Mac Pro (Mid 2010)
    • Mac Pro (Mid 2012)
    • Mac mini (Mid 2011)
    • Mac mini (Late 2012) 
    • iMac (27-inch, Mid 2010)
    • iMac (21.5-inch & 27-inch, Mid 2011)
    • iMac (21.5-inch & 27-inch, Late 2012)
    • iMac (21.5-inch) Early 2013
    • Windows 7, Windows 8, and Windows 8.1, 64 bit

     

    W8.1 uses two different versions of drivers. The .5621 is for the listed Macs. This is what you would have used for W7/W8.1. If you download this version to an external USB drive, and in Windows right-click on the

    USB -> Bootcamp -> Drivers -> Apple you can see the Bootcamp.msi version.

     

     

    But I do not understand how to react to the next part of your reply:

     

    "Switch to Windows and run setup.exe and check if your update finishes. If Windows was installed with proper BC drivers, it should already be in place."

     

    The sequence of error events in my original post are from running the latest setup.exe in Windows. Are you implying that I should find and try installing the old 5.1.5621 Boot Camp? If so, where can I find it?

     

    Any idea why the path the new setup errors out at is: C:\ProgramData\Apple\Installer Cache\Boot Camp 5.0.5033 ?

    You can remove this cache. Did you upgrade from W7 to W8.1 in the past? If you have run 5.1.5621 setup.exe in the past, you do not need to run it again.

     

    From Boot Camp Support Software 5.0.5033,

     

    File Size: 553.62 MB

    System Requirements

    • MacBook Air (Mid 2011) and (Mid 2012)
    • MacBook Pro (Mid 2010)
    • * MacBook Pro 13 inch-Mid 2010 is not supported
    • MacBook Pro (Early 2011)
    • MacBook Pro (Late 2011)
    • MacBook Pro (Mid 2012)
    • MacBook Pro (Retina, Mid 2012)
    • MacBook Pro (Retina, Late 2012)
    • Mac Pro (Early 2009)
    • Mac Pro (Mid 2010)
    • Mac mini (Mid 2011)
    • Mac mini (Late 2012)
    • iMac (Mid 2011)
    • iMac (Late 2011)
    • iMac (Late 2012)
    • Windows 7 and 8, 64 bit only

     

     

     

    I looked at the XML file in the new Boot Camp flash drive (where the new setup.exe resides). There are a lot of version number cited:

    <ProductVersion>6.0.6136

    <FileVersion>5.1.5.0

    and others

     

    My uninformed gut reaction to this problem is that the new setup.exe is detecting a mismatch between the Boot Camp version currently installed and references to it in the Registry. But that's just a guess.  The Windows Installer crash suggests a bug in their code (an inability to properly handle this situation).

     

    Could I edit the new XML file to ignore or deal with the version mismatch, if indeed that's the problem?

    BC 6.x drivers are meant for W10 (and W8.1 on newer models). On a 2012 model, W8.1 use the BC5.x series. If you use BC Assistant 6, it will download BC6 (6.0.6136) drivers as you can see. These are incompatible on 2012 models with BC5 drivers that are already on your Mac.

     

    I suggest running Windows Update (ignoring driver updates) and then upgrading to W10 using an in-place upgrade.

  • by trwd,

    trwd trwd Jul 31, 2016 7:52 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Jul 31, 2016 7:52 AM in response to Loner T

    Thank you for the additional insights, LonerT.

     

    I should probably now add that I ran the in-place upgrade to Windows 10 a few days ago and found that brightness control, among other features, no longer worked. Later, with a dwindling battery and no transformer available, I made the horrible mistake of enabling Windows 10's Battery Saver mode, whereupon the screen went dark, never to return until a hard power off. Subsequent efforts to get the thing working outside of Safe Mode ended up corrupting something serious so I restored Windows 8.1 from a WinClone backup.

     

    That is is why I decided to install the latest Boot Camp drivers -- prior to upgrading to W10 again.

     

    From your next-to-last paragraph it sounds like I should proceed with upgrading to W10 without messing with the BC6 update. But THEN, once W10 is installed, what do you suggest I do in order to restore functions like Brightness control, etc.?  Do you think the BC6 setup will run without failing?

     

    BTW, the current Windows 8.1 system is already fully updated (per Windows Update). It's ready to upgrade to W10, and since it was upgraded previously, before the July 29 deadline, I assume it will reactivate.

  • by Loner T,Helpful

    Loner T Loner T Jul 31, 2016 8:49 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Jul 31, 2016 8:49 AM in response to trwd

    trwd wrote:

     

    I should probably now add that I ran the in-place upgrade to Windows 10 a few days ago and found that brightness control, among other features, no longer worked. Later, with a dwindling battery and no transformer available, I made the horrible mistake of enabling Windows 10's Battery Saver mode, whereupon the screen went dark, never to return until a hard power off. Subsequent efforts to get the thing working outside of Safe Mode ended up corrupting something serious so I restored Windows 8.1 from a WinClone backup.

     

    That is is why I decided to install the latest Boot Camp drivers -- prior to upgrading to W10 again.

     

    ...

    BTW, the current Windows 8.1 system is already fully updated (per Windows Update). It's ready to upgrade to W10, and since it was upgraded previously, before the July 29 deadline, I assume it will reactivate.

    If Windows Update does not provide any new updates, you can update to W10, without need a new activation. It should activate automatically.

     

     

    From your next-to-last paragraph it sounds like I should proceed with upgrading to W10 without messing with the BC6 update. But THEN, once W10 is installed, what do you suggest I do in order to restore functions like Brightness control, etc.?  Do you think the BC6 setup will run without failing?

    Leave BC6 and BC5 both alone. After W10 upgrade is complete, try the 6.0.6136 update, but be prepared for a bit of bumpy ride. Right after the W10 upgrade, please create a Windows System Restore point, before BC6 drivers are installed/upgraded. You can run setup.exe from the 6.0.6136 USB. You may see conflicts between BC5 (upgraded) and BC6 updated drivers.

     

    You may also want to be prepared for a clean W10 installation, if necessary, if you see any issues. The BC5-to-BC6 transition is painful.

  • by trwd,

    trwd trwd Jul 31, 2016 8:52 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Jul 31, 2016 8:52 AM in response to Loner T

    Loner T wrote:

     

    trwd wrote:

     

    I should probably now add that I ran the in-place upgrade to Windows 10 a few days ago and found that brightness control, among other features, no longer worked. Later, with a dwindling battery and no transformer available, I made the horrible mistake of enabling Windows 10's Battery Saver mode, whereupon the screen went dark, never to return until a hard power off. Subsequent efforts to get the thing working outside of Safe Mode ended up corrupting something serious so I restored Windows 8.1 from a WinClone backup.

     

    That is is why I decided to install the latest Boot Camp drivers -- prior to upgrading to W10 again.

     

    ...

    BTW, the current Windows 8.1 system is already fully updated (per Windows Update). It's ready to upgrade to W10, and since it was upgraded previously, before the July 29 deadline, I assume it will reactivate.

    If Windows Update does not provide any new updates, you can update to W10, without need a new activation. It should activate automatically.

     

     

    From your next-to-last paragraph it sounds like I should proceed with upgrading to W10 without messing with the BC6 update. But THEN, once W10 is installed, what do you suggest I do in order to restore functions like Brightness control, etc.?  Do you think the BC6 setup will run without failing?

    Leave BC6 and BC5 both alone. After W10 upgrade is complete, try the 6.0.6136 update, but be prepared for a bit of bumpy ride. Right after the W10 upgrade, please create a Windows System Restore point, before BC6 drivers are installed/upgraded. You can run setup.exe from the 6.0.6136 USB. You may see conflicts between BC5 (upgraded) and BC6 updated drivers.

     

    You may also want to be prepared for a clean W10 installation, if necessary, if you see any issues. The BC5-to-BC6 transition is painful.

     

    Thank you, again!

     

    Has the painful BC5-to-BC6 transition been written about anywhere?

     

    Let's pretend that I encounter problems with BC6 setup. Is it feasible to install individual drivers?  The only MBP features I really care about are brightness control, touchpad, wi-fi and blu-tooth.  If it's possible to install those drivers individually is there info anywhere about identifying which drivers do what? (some mfr names are obvious, but not all)

  • by Loner T,

    Loner T Loner T Jul 31, 2016 9:01 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Jul 31, 2016 9:01 AM in response to trwd

    If you look at the USB Flash drive and look at the directory structure under Bootcamp directory, it has vendor names on sub-directories. For example (I modified the structure to allow a combined v5-v6 setup) to have the files in one place. $WinPEDriver$ is critical during boot/installation.

     

    Bootcamp-v6-v5-combined.png

  • by trwd,

    trwd trwd Aug 29, 2016 8:09 PM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 29, 2016 8:09 PM in response to Loner T

    I'm BAAACK! And so is the bootcamp update problem.  After your last reply I restored Windows 8.1 using WinClone and got away from this project for a while. Today I decided to return to it. I installed the Windows 10 upgrade, followed by the Anniversary Update 1607. I then ran Apple Software Update and it specified two updates needed: Bootcamp and iTunes. This sounded great because I could bypass the USB stick and let Apple download what's needed.

     

    About a third of the way through the progress bar I got this message.

     

    err msg 1.png

     

    Weird. Then, immediately the following message appeared below the Apple Software Update window.

     

    err msg 2.png

     

    I clicked the Browse button to see if the referenced file exists. It does.

     

    err msg 3 path.png

     

    But upon selecting and "opening" it the following message appears.

     

    err msg 4.png

     

    Apparently even when Apple Software Update tries to install the latest Bootcamp it does not like the existing "installation package".  Why can't the Updater just install the new Bootcamp update; why does it need the old one!?

     

    Reinstalling Windows and all my programs and settings would be a huge job and hard to accept given that Windows 10 appears to be working fine. The only device apparently not working is Bluetooth.

     

    Does the Bootcamp update install anything other than updated drivers?

     

    If only new drivers are needed can I just go through the drivers you showed on the USB stick and selectively install the relevant ones?

     

    Any idea what drivers need updating? (is there a list somewhere?)

  • by Loner T,

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

    In the last screen shot, the reference is to 5.0.5033, which was used for the original W8.1. There is a convoluted install/uninstall dance being played in the background.

     

    You can either download 5.0.5033 and point to the MSI file that the error message wants to use, in the directory where you download it, or, you can use the OS X side, download the BC6 package using BC Assistant, and run setup.exe from the BC6 folder, and test.

     

    Bootcamp services are the Apple Software Update services, the OS Manager, etc..

  • by trwd,

    trwd trwd Aug 30, 2016 10:15 AM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 30, 2016 10:15 AM in response to Loner T

    Thank you for replying Loner T.

     

    Per your recommendation I downloaded Bootcamp 5.0.5033, unzipped it, and copied its bootcamp.msi file to the path Apple Software Update expected it to be found in.

    C:\ProgramData\Apple\Installer Cache\Boot Camp 5.0.5033\

     

    I ran Apple Software Update and left the room. Upon returning I found this message atop the Apple window.

    err msg 1.png

    I clicked the "Close the program" button. After a pause Apple Software Update appeared to finish, and then it said the system needs rebooting to complete installation. I rebooted the system.

     

    After reboot I checked Device Manager to see if the Bluetooth driver had miraculously been installed. Nope.  I ran Apple Software Update and once again it says Boot Camp needs updating.

     

    So while I did not get all the other error messages after "Windows installer has stopped working", the installation was still a failure.

     

    Did I make a mistake in the process?  What step would you recommend next?

     

    Anticipating that you might say try your other recommendation:

     

    ...or, you can use the OS X side, download the BC6 package using BC Assistant, and run setup.exe from the BC6 folder, and test.

     

    Could running BC6 setup in OS X overwrite or otherwise destroy my Windows installation?  And what do you mean by the word "test"?

  • by Loner T,

    Loner T Loner T Aug 30, 2016 10:20 AM in response to trwd
    Level 7 (23,493 points)
    Safari
    Aug 30, 2016 10:20 AM in response to trwd

    You can download BC6 drivers to a USB using OSX BC Assistant. Switch to Windows after you have the drivers on the USB, and then run setup.exe from Bootcamp folder. Please create a Windows System Restore point, before you run setup.exe.

     

    BC6-Assistant-Download-Software.png

  • by trwd,

    trwd trwd Aug 30, 2016 7:53 PM in response to Loner T
    Level 1 (15 points)
    Windows Software
    Aug 30, 2016 7:53 PM in response to Loner T

    I could not create a restore point because "the shadow copy provider had an error".  The Application log had numerous VSS and CAPI2 errors associated with it.

     

    I ended up using WinClone to backup the Bootcamp partition.

     

    I ran the Bootcamp setup program from the USB stick but ultimately ran into the same Windows Installer failure. After closing that message the Setup program kept progressing but then a very plain message with only the word "error" in it appeared. Eventually the Setup program said it had finished installing Bootcamp and it's time to reboot.  I'm not falling for that again!

     

    I appreciate your efforts greatly! 

     

    Any suggestions?

  • by Loner T,

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

    trwd wrote:

     

    I could not create a restore point because "the shadow copy provider had an error".  The Application log had numerous VSS and CAPI2 errors associated with it.

     

    I ended up using WinClone to backup the Bootcamp partition.

    This is a known issue with older version of AppleHFS.sys/AppleMNT.sys. Please see Windows 10 Can't Boot After Installing Bootcamp Drivers as a reference. A mix of BC 5.x and 6.x drivers causes quite a bit of grief.

     

     

    I ran the Bootcamp setup program from the USB stick but ultimately ran into the same Windows Installer failure. After closing that message the Setup program kept progressing but then a very plain message with only the word "error" in it appeared. Eventually the Setup program said it had finished installing Bootcamp and it's time to reboot.  I'm not falling for that again!

    You can try the method outlined, installing specific drivers manually and then running 6.x setup.exe which then does not try to install drivers that fail validation. You will need to look through logs to see which specific drivers are failing. Realtek setup fails regularly, so it can be removed from a 2012 model setup structure.

     

    The logs on my 2012 MBP in the Bootcamp folder are

     

    pwd

    /Volumes/BOOTCAMP

    find . -name "setup*.log" -print

    ./$Windows.~WS/Sources/Panther/setupact.log

    ./$Windows.~WS/Sources/Panther/setuperr.log

    ./Windows/INF/setupapi.dev.log

    ./Windows/INF/setupapi.offline.log

    ./Windows/INF/setupapi.setup.log

    ./Windows/Logs/SetupCleanupTask/setupact.log

    ./Windows/Logs/SetupCleanupTask/setuperr.log

    ./Windows/Panther/setupact.log

    ./Windows/Panther/setuperr.log

    ./Windows/Panther/UnattendGC/setupact.log

    ./Windows/Panther/UnattendGC/setuperr.log

    ./Windows/setupact.log

    ./Windows/setuperr.log

    ./Windows/System32/Sysprep/Panther/IE/setupact.log

    ./Windows/System32/Sysprep/Panther/IE/setuperr.log

  • by trwd,

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

    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?

     

    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?

     

    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.

Page 1 Next