Mac VNC not working after Security Update 2016-002

If Sharing=>Remote Login (ssh) is enabled you can do the following:

1) ssh into the remote machine

2a) sudo pkill loginwindow OR

2b) sudo shutdown -r now

Now you can vnc in.

Also on Yosemite and discovered this fun new issue after applying the update. I guess this is one way to get users to migrate faster to El Captan.

I'm running 3.8.5, got updated the same time as the security update.

For now I've got the realVNC server running. Really, I'd be just as happy to run El Cap again as long as I wasn't running into audio problems. In 10.11.4, I found my mac mini would freak out if I was listening to streamed audio and I turned my TV off (to listen to music just through the stereo). I don't have that problem in Mavericks.

Yup, upgrading to El Capitan appears to have "fixed" the issue for me as well. Now to pick up the pieces after upgrading the OS. (ie, I see my old printer icons are now all just document icons.)

We are running a Mac Mini in ghost mode. I connect from MBP with screen-sharing, my colleagues did connect with vnc-viewer from PC's. After the update from March 22 vnc connection did not work. We updated the Mac Mini from Yosemite to El Capitan but this did not help. No I found out when I allow screen-sharing access only for the Administrators group vnc-viewer connections from PC's user do work again.

It appears I found a solution.

Go to System Preferences, Sharing, Under “Screen Sharing” select “Computer Settings”, and untick “VNC users may control screen with password...”. After that, I connected, was asked for username and password, and could properly control the screen.

Hope that helps.

this worked for me

Ha- the question now is how many things stopped working when you went to El Capitan??

😝

None of the solutions offered here worked for me.

If you have a backup from before March 26, then you can revert to the old version of ARD by replacing this folder:

/System/Library/CoreServices/RemoteManagement

with the one from your backup and restarting.

My connections work normally again after doing this.

jrh

I pulled this from another server here (older test server; 10.0.3, I believe) and the version of ARDAgent was 3.8.4. Replaced that folder on this server and remote VNC works again!

For those who cannot/do not have access to an older version...

http://rmscomputersystems.com/~pscordam/RemoteManagement(ARDAgent3.8.4).zip

This is the "Remote Management" folder in its entirety. 4 Objects (1 app and 3 bundles)

Caveat emptor! Backup everything, and twice if you half-don't know what you are doing. I am not responsible for making an annoying situation more annoying or possibly even up to and including a full server loss (software or hardware) but if you need it, there it is.

Thanks, that worked for my Mavericks.

This worked me as well....

Go to System Preferences, Sharing, Under “Screen Sharing” select “Computer Settings”, and untick “VNC users may control screen with password...”. After that, I connected, was asked for username and password, and could properly control the screen.

I was having problems specifically with RealVNC. Every time I logged in, I would run into that same error. So far, through the phone's app, it works.

Still running 10.10.5. on the host computer too.

Apple just issued a new updated 3.8.5.1 Anyone try it yet???

I just updated to 3.8.5.1 and it fixed the issue.

I just upgraded, I can confirm that this version seems to fix the problem.