Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Well a couple of interesting things with this one on a Mac Pro:

1. USB over Thunderbolt is still broken.

2. My MX Master mouse no longer works properly via Bluetooth. I can re-pair it and it will work briefly, but it eventually loses the connection and will not work again until it is paired again.

Yeah I'm having the same exact problem with bluetooth and my mouse, seems like the bluetooth and 2.4 GHz wifi instability problems have reared their ugly head again :( also my USB 3.0 to Gigabit ethernet adaptor (using the Asix AX88179 chipset) is now non functional. The kext is not getting loaded on startup and OSX is complaining that it's unsigned, where as on 10.11.3 betas they were working and signature was in good order. I'm guess thats why everyone is having VPN issues because apple messed with kext signing.
 
Hope they fix finder. It's constantly not showing all my side folders (Apps, Music, Movies, drives, etc.). Even after a force quit and restart of finder.
 
I hope they fix safari eventually. It has been so buggy for the past couple of releases that I can't even use it anymore. I like to use top sites and it works for awhile but then stops responding to input and I have to quit the whole browser to get it to respond again

I want to love Safari (abandoned it years ago for Chrome). Chrome is a bit of a resource hog, even after many attempts to taper that down, but it it more compatible with most sites, loads faster, and it's feature sets are more manageable and work as advertised. Safari always has some bugginess about it, random freezes, takes forever to load.... and all the attempts at simplicity and ease of use with Safari seem to backfire on it. It was once my favorite browser, but now I only use it when I need to remote into work because it's the only supported browser on the mac to do so. It just needs some minor things to bring to it greatness.... but noooooo.... Apple always focuses on features no one uses and leaves the bugs behind to breed.
 
  • Like
Reactions: colourfastt
Yeah I'm having the same exact problem with bluetooth and my mouse, seems like the bluetooth and 2.4 GHz wifi instability problems have reared their ugly head again :( also my USB 3.0 to Gigabit ethernet adaptor (using the Asix AX88179 chipset) is now non functional. The kext is not getting loaded on startup and OSX is complaining that it's unsigned, where as on 10.11.3 betas they were working and signature was in good order. I'm guess thats why everyone is having VPN issues because apple messed with kext signing.


This sort of thing is why I stopped testing betas here. It used to be you could get early "fixes" by testing these betas. rarely did things like you have described fall apart. Now it seems the norm. I don't understand what the heck they are up to. Experimental crap like this should be Dev only probably.
[doublepost=1452991381][/doublepost]
You sure its not a HW problem?
I had the same issues. It works if you step back to release versions.
[doublepost=1452991466][/doublepost]
So it seems that it is not just me having issues with 10.11.4 and Bluetooth. This seems to represent the same issue I have where there are disconnects after an idle period.

See: https://openradar.appspot.com/24169259
You see, there really is no good reason they should be messing with this to the point of failure like this report. Just seems like more "core rot" to me. Don't get it....
 
Is anyone having issues with this beta release where your Macbook Pro Hangs. My laptop has been perfect for months but this week (since the update) it keeps freezing and I have to do a hard reboot.
 
I want to love Safari (abandoned it years ago for Chrome). Chrome is a bit of a resource hog, even after many attempts to taper that down, but it it more compatible with most sites, loads faster, and it's feature sets are more manageable and work as advertised. Safari always has some bugginess about it, random freezes, takes forever to load.... and all the attempts at simplicity and ease of use with Safari seem to backfire on it. It was once my favorite browser, but now I only use it when I need to remote into work because it's the only supported browser on the mac to do so. It just needs some minor things to bring to it greatness.... but noooooo.... Apple always focuses on features no one uses and leaves the bugs behind to breed.
I tried other browsers a few times, didn't like them and am only using Safari, it is by far my most favourite browser. For some reason I hate the look of chrome and it's behaviour (my other half likes it for some reason).
 
You sure its not a HW problem?
I had the same issues. It works if you step back to release versions.

Back when i did some contracting for Cisco, they had a rapid response team that they'd send out for especially devilish installations. Basically, it was a highly qualified System Engineer with a kit bag of goodies. Was it expensive? Yeah, definitely. And project managers had to basically talk to vice presidents to get the SE sent. (Think some crazy '13 Hours' stuff.) Cisco at its height in the late '90s/early 2000 wasn't nearly as big or rich as Apple is today…why they aren't more reactive to these kinds of hardware issues is beyond me. In short, they'd do better with users who see this stuff to just overnight a new iMac and ask you to test it. I think most Mac users would HAPPILY do it for nothing…or heck, at most a t-shirt. If the problems are MORE widespread than that, however—and I can't help but believe they are—then it really kinda should make you question Apple. Because that would mean they KNOW about hardware problems, and aren't fixing them. In fact, you might could be excused if you said they were covering them up. (Given Apple's fairly rocky past with hardware problem cover-ups, from GPUs to CPUs to LCD coatings, et al, I don't think ANYONE should be looked at askew for suggesting such a "conspiracy theory". Apple deserves the lack of trust, all on its own.)

That users who have reported these kinds of USB problems are not hearing from Apple Engineering is disheartening. I expect better.

(The argument that "well, these are beta releases" doesn't wash. If Apple had a firm understanding of the problems, they'd be getting RESOLVED and specifically mentioned in release notes. They aren't. So if they DO NOT have that "firm understanding of the problems", Apple Engineering should be looking for as many in-the-field test cases as possible to get to that level of understanding. And, again, they obviously aren't, as I've watched users report these problems now for weeks/months.)
 
  • Like
Reactions: Ebenezum
I noticed something strange. I can't use http://trailers.apple.com/ since upgrading to this beta. I tested 4 web browsers. The grey frame below the poster image is empty. No trailer thumbs to click on. The page works with my ipad and iphone.

Clip_2016_01_18_kl_10_01_13.jpg
 
That users who have reported these kinds of USB problems are not hearing from Apple Engineering is disheartening. I expect better.

I have heard back from them. The problem is that one, it was weeks later, and two, they could not duplicate the issue. What I think is happening is that they feel like they can liberally play with drivers to some end because it is a beta. I've noticed that they sometimes revert to the working version in the release after a broken beta, only to start tinkering with it again in the next series of betas. The worst part is that a lot of it seems very hardware/system specific/software specific and all around tough to pin down. In the case of the usb flash drive problems, not everyone uses all 4 usb ports on an imac regularly and multiple flash drives in different inputs and the beta and on and on...

I was encouraged by their response (albeit very late) but it was clear to me that the teams that work on these new features and bug fixes and protocol advances in the OSX beta lines are quite isolated from the so-called beta testers and the beta bug reports analysts. I'm pretty sure that only the most obvious easily reproducible stuff gets to them.

At the end of the day, after years of testing these betas, it is clear to me that lately it has become a bit more risky than usual to be on this beta train. I used to look to betas to fix ongoing issues. Now I see them causing more issues than they are fixing. It seems to have become quite experimental in nature. So be it....
 
Re: VPN problems - Apple now requires the tap and tun kexts to be signed by their author. My provider gave signed ones and everything's working again.
 
  • Like
Reactions: vtowntim
Re: VPN problems - Apple now requires the tap and tun kexts to be signed by their author. My provider gave signed ones and everything's working again.

Yup, I figured as much about the kext signatures being altered again. Seems like this beta went under the hood vs the cosmetic fixes that we saw in previous beta versions. I knew the risks for software being broken but I did not expect them to go in and make the authors of resign kexts. I really dislike the "walled garden" approach to kexts, I'd wish there was a button in security vault to run unsigned kexts instead of having to use boot flags\messing with underpinnings of OSX to get things to work.
 
I'd wish there was a button in security vault to run unsigned kexts instead of having to use boot flags\messing with underpinnings of OSX to get things to work.
Better yet, why don't they just implement a local self-signing feature. You point to the KEXT, say "I approve" and it gets signed. Heck, even if it would require Xcode to be present ("This is a development machine."), it would be worth the hassle.
 
I noticed something strange. I can't use http://trailers.apple.com/ since upgrading to this beta. I tested 4 web browsers. The grey frame below the poster image is empty. No trailer thumbs to click on. The page works with my ipad and iphone.

Clip_2016_01_18_kl_10_01_13.jpg
Clicked the link you supplied. Works for me, in Safari. I have installed the beta on an external SSD, with few launch items, which may account for the differing results. Do you have other sites that are problematic? Happy to test.
 
Better yet, why don't they just implement a local self-signing feature. You point to the KEXT, say "I approve" and it gets signed. Heck, even if it would require Xcode to be present ("This is a development machine."), it would be worth the hassle.

I was able to mess with SIP and got the kext to run,

Apple has changed the Kext Version signature and as a result Cisco needs to put out a revised lower level driver, if you need Cisco client as a mission critical app NOW you'll need to disable SIP (AKA kext signing\lowlevel driver protection) to get it to work. This method will work and is what I used to get my USB3 to Gigabit Ethernet Hub to work.

http://osxdaily.com/2015/10/05/disable-rootless-system-integrity-protection-mac-os-x/

Please be VERY VERY careful when disabling system integrity protection, drivers that have not been optimized and or containing malicious code will not be filtered out by OSX and your machine will be vulnerable... Sorry for the Doomsday message, but fair warning needs to be given.
 
  • Like
Reactions: vtowntim
Anyone having issues with the cursor symbol being incorrect after upgrading? My cursor is now mostly a Crosshair symbol (+) instead of an Arrow, and in Safari, links are NOT changing to the Hand symbol consistently. Also, the cursor symbol seems to erratically change as you move it around a page. Also, while i am typing this, the cursor is a Crosshair instead of a Insert symbol. Oh Wait! It changed! Frustrating.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.