Worse is blown ear drums if someone had headphones on.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Updates Boot Camp Drivers to Fix Major Issue Causing Blown Speakers on New MacBook Pros [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Worse is blown ear drums if someone had headphones on.
What you say is 100% absolutely true. But how is it relevant to the topic? Or is this just a reply to the original comment that was irrelevant to the topic? Products have issues. Everyone's products have issues. If someone can find a tech product that was released without issues... well, they can't. I know they can't. Apple just has the spotlight, which shines brightly on the good and bad. They issued a quick fix as they should. Issue will be forgotten in a few days. Until the next issue pops up, and it will.
I agree that in today's Apple, creatives aren't the primary consumer of the Macbook Pro, whether by intention or not. But to that end, there are very few Starbucks sipping hipsters with these brand new notebooks in their hands that are running Windows via BC, given they weren't available for consumer use until 2 weeks ago. Apple realized the issue, and dealt and is dealing with it in an agile manner.
Insofar as businesses buying Macs primarily to run Windows, which naturally will have less native support compared to a PC.. that is virtually a unicorn scenario. I don't know of any business that does this with their notebook fleet. If they're using MacOS, they're buying Macs. If they're using Windows, they're buying PCs. I'm not saying in no corner of the planet, someone isn't using a Mac with BC to run Windows for a "business" task, but it's incredibly rare. If you can provide specific support for a business, such as IBM, that has purchased Macs and installed Windows via BC as the primary OS, then that could change the facts of the argument.
They had their speakers too high on the MBP and caused the problem. They dropped their phone too hard/too many times and caused the touch disease.Uh, okay.
Think about it. If there aren't that many MBP's out in the wild and this is already happening to enough of that portion for Apple to correct the issue then that tells me 2 things. 1. Apple believes the issue is wide spread enough to warrant immediate action. 2. Apple did the right thing by jumping on this pretty quickly.
Looking at the launch of the MBP, criticism is warranted. Looking at this issue singularly, criticism is warranted. Apple promptly issuing a fix is the right thing to do.
Apple is admitting there is an issue with the drivers, and issued a fix to prevent it from occurring in the future. If a notebook was damaged from due to this driver issue, they are replacing it at no-cost to customers. I'm not informed enough about the touch disease topic, and as this doesn't relate to the topic at hand (nor does the MBP launch in general-everyone realized it wasn't Apple's finest moment), I don't know if that's relevant. Clearly no company is going to be praised for ever having a product with an issue, but certainly based on how the dealt with it.
Did you read what you linked? That's intentional bricking of counterfeit products. I welcome this since counterfeit products don't perform at the same level as genuine products while increasing support cost due to compatibility issues and could bankrupt the original manufacturer. Case in point, a client and I were troubleshooting a Cisco router issue that turned out to be an issue with the counterfeit USB to serial adapter that he unknowingly bought.
I have not heard of an instance where the software could physically damage the hardware since I think early DOS days. I wonder if the fix for this was to just make the maximum sound output much lower than before. This whole issue is kind of worrying tbh. I'd think there should always be some hardware gate in place that would prevent things like this, no matter what the software is trying to do.
Last edited:
I run a media services business and while we have offices with dedicated Mac Pro and iMac workstations (with A/V interfaces connected to external equipment) we also have laptops that are in use specifically for their portability. A quick meeting with a client in their office to review edits or discuss ideas is usually done with just a laptop and internal speakers.
Thanks for that input. Are you using Windows on these devices via BC?
My initial point was that there must be a very tiny sliver of people that fall into all of the below categories, and thereby no one else is immediately affected (even if affected, Apple has/will take care of you at no-cost):
1.) Uses their 2016 (since other models not affected) Macbook Pro for a living/their profession.
2.) Rely on Windows via BC, not MacOS, for productivity software to deliver a product/service relating to their profession.
3.) Had their volume loud enough to be blown out by the issue.
Not to worry, a replacement machine with very more better potent unapologetic magic speakers is already on the way.
The next iteration will have no display at all because you can talk to Siri. Reduce to the max by Jony Ive.
Let us have a seance and contact Steve Jobs....seems that a bit of quality control left with him along with a big dose of inspiration.
Apple has released updated audio drivers to fix a major issue causing blown out speakers on new MacBook Pro models running Windows 10 with Boot Camp.
Earlier this month, a number of users began noticing crackling or distorted sound coming from the left, right, or both speakers on the new MacBook Pro, oftentimes shortly after installing and running Windows 10 with Boot Camp. These issues persist even when affected users boot back into macOS Sierra.
MacRumors reader tianhuailiu -- edited slightly for clarity:The damage to the speakers appears to be permanent once it occurs, requiring users to contact Apple to exchange their new MacBook Pro for a replacement unit. Unfortunately, due to limited stock, some of these users are now faced with waiting several weeks for their MacBook Pros to be swapped out.
The new Boot Camp audio drivers are available through Apple Software Update on the Windows side for both 13-inch and 15-inch models, although the issue appears to primarily affect the larger of the two. The new drivers, of course, are of no help to users who have already blown out their speakers.
While new drivers are available, late 2016 MacBook Pro users should exercise caution when running Windows 10 with Boot Camp due to the severe nature of the problem. As a temporary workaround, some users have plugged in headphones during the booting process until installing the updated drivers.
After installing the updated drivers, some MacBook Pro users appear to be experiencing issues with low volume on both Windows 10 and macOS Sierra, but the underlying problem remains unclear. Affected users should contact Apple or schedule a Genius Bar appointment for further support.
The issue does not affect older MacBook Pro models or Windows virtualization software such as VMware Fusion and Parallels Desktop for Mac.
Article Link: Apple Updates Boot Camp Drivers to Fix Major Issue Causing Blown Speakers on New MacBook Pros
An analogue cable would also do the trick.
I'm surprised and disappointed that no one reported on the loss of optical digital in any review I've seen.
[doublepost=1480626371][/doublepost]
Yeah I wonder if they've hit panic stations and a silent hardware fix is needed. Did they forget some kind of over-current protection for the new speaker design?
There's a reason why we only buy Dell machines with same or next business day on site warranty... Try buying such a service package from Apple. Genius bar my ass...
If you want/need a completely native Windows environment for performance reasons - especially if you want to run GPU dependent Windows applications at the highest performance level.
Bootcamp is overall faster, also supports DX11, DX12. Fusion is not 100% native speed - there is over head.
I found Parallels / Fusion to be iffy with a few windows applications, and needed to use BC for stability.
Any ideas on what might cause this issue without Windows? See my post from a couple of days ago for full description and measures taken to resolve
https://forums.macrumors.com/threads/15-2016-mbp-speaker-crackling.2015467/page-7
[doublepost=1480627186][/doublepost]Oh, I forgot to say I have reset PRAM too
https://forums.macrumors.com/threads/15-2016-mbp-speaker-crackling.2015467/page-7
[doublepost=1480627186][/doublepost]Oh, I forgot to say I have reset PRAM too
