MacOS 26.6.1 breaks VNC.

I don't use realVNC, but rather Apple's own Screen Sharing app located in the /Applications/Utilities folder on macOS Tahoe.

I did need to revisit Settings > General > Sharing panel and re-enable Screen Sharing. Then click the i⃝ button to add my personal name to the existing Administrator access entry. Both Macs have the same administrator and user name, so this was something Apple has changed. I also toggled on the VNC viewers may control screen with password — something I didn't need in the past for Screen Sharing to just work.

With the previous paragraph changes, I could click on the remote host name entry in the Screen Sharing panel on my M4 Mac Mini Pro and share my 2020 27-in iMac screen on my 32-in LG display. Both Macs running Tahoe 26.6.1.

In addition to realVNC, you may want to ensure there is no issue with that SSLVPN too. Apple changes things, vendors may not keep up.

Tested: Screen Sharing, macOS 26.6.1

A working alternative is the free app Remote Desktop Manager (Devolutions), which supports Apple Remote Desktop connections on iOS and iPadOS.

You might want to contact VNC's support so that they can look into it, and alternatively, give this as feedback to Apple. Since Apple is not participating on this user to user support forums, please do so using this link

Product Feedback - Apple

Mel Beckman wrote:

MacOS 26.6.1 breaks VNC.

Wow! What a blast from the past. I haven't heard of anyone using VNC in years!

This update, just released today, breaks VNC. After installing macos 26.6.1 the machine reboots with Remote Access disabled. I did turn it back on, but then when I tried to use RealVNC, after it takes my VNC password it just spins forever without connecting. This has disabled remote admin for all of our users.

Anyone with "users" of their own needs to be very careful with macOS updates. The only thing surprising here is that all this hasn't already happened 5 years ago. You've made it this long applying zero-day updates? That's impressive! Kudos to your support staff!

I found the fix with the help of ChatGPT:

Please don't quote AI chatbots. Even going beyond today's current AI slop fad, it's just very annoying on any discussion forum or support message when someone asks for help by just quoting something that Apple or some other company said in a computer-generated e-mail template. I understand those messages aren't helpful. But why do people think they would be any more helpful to people like us who don't know anything about what's going on?

This scared me

If we're expressing emotion now then I guess the AI slop text is done. We can get back to the conversation.

we have dozens of remote support techs in government environments that have only iPads for remote access to hundreds of systems.

And you're asking for help on the consumer-focused Apple Support Community? Why don't you just call your Apple rep?

The 26.6.1 update is rolling out automatically

I wouldn't recommend that.

I have my work cut out for me fixing the VNC settings, but that's easy to do via a Mac running Screen Sharing, which still works the same.

Hint! Hint!

Alas, the following CLI no longer works since MacOS 12:

kickstart -deactivate

<some command to enable standalone Screen Sharing>

<some command to set VNC password>

Terminal is not useful for a wide swath of Apple configuration settings.

Instead you need Apple's full-fledged MDM

Okay.... I guess I'm still confused. You started a post saying essentially, "junk tech from 1987 no longer works". Solution is to use the modern, supported management tool. I'm certainly in agreement with that analysis, but do you have a question we could help with?

Mel Beckman wrote:

Apple has no Screen Sharing app for iPad. VNC is the only option unless you subscribe to a Cloud-based remote support app, which our corp security rules prohibit.

True, and way back in the iPad 2 days, I actually had a realVNC client installed, but no longer use VNC from an iPad.

Developers, at the company I work for, use VNC extensively connecting Mac and Windows company laptops to Linux hosted development & test systems thousands of miles away in a company data center.

The company has standardized on TigerVNC as the client & server. On the Mac TigerVNC does a better job of copy & paste between Linux and macOS, then the macOS provided Screen Sharing app talking the VNC protocol to with a Linux system.

And as a side note, we did have one developer that used RealVNC from their personal Windows system at home, VPN’ed into work, connecting to their company Mac. That worked well for several years.

VNC is alive, and delivering results for thousands of developers in just 1 company.

PS. I personally use an even older technology. ssh from my Mac to my hosted development & test systems. ssh is my networking Swiss Army Knife 😁

Mel Beckman wrote:

VNC is hardly obsolete, any more than bash is.

The current version of bash on macOS is 19 years old. So yeah, I would call that obsolete.

It’s the only open protocol available to iPad users, since Apple has no Screen Sharing app app for iOS.

There are lots of remote access solutions available. I don't see the point in requiring some "open" protocol, especially on the basis of Apple not providing one. Apple isn't exactly the most "open" company in the world.

Notice that I wasn’t asking for help here

This is a tech support forum. That's the whole point. If you did happen to find someone else still trying to get VNC to work after so many other people gave up on it in disgust 20 years ago, you're welcome to point your chatbot in their direction. You might have to wait a while. I tried to find the most recent VNC question and the best I could find was one in early 2026 and few in 2025. And that's just for VNC. Most people these days just ask the chatbots themselves.

Also, I said ChatGPT HELPED solve this, and the fix is verified. So not AI Slop as you unhelpfully opine.

Sorry, but when I see somebody neck deep in some ancient tech rabbit hole, I try to help them get out rather than giving them an AI shovel to keep digging with.

BobHarris wrote:

I personally use an even older technology. ssh from my Mac to my hosted development & test systems. ssh is my networking Swiss Army Knife 😁

Perhaps in hindsight I shouldn't have said anything about 1987. That's not even accurate anyway. Apparently VNC dates from 1998.

But I was accurate when describing it as "junk tech". That's the important part. It doesn't matter if it was invented in 1987, 1998, or 2026, junk tech is junk.

I haven't used any cross-platform remote access tools for a couple of years. Tools based on Microsoft's RDP protocol were very easy to use. But I can't say RDP is "superior" to VNC, because the last time I tried VNC was on my Linux server back when I got my fiber connection a few years ago. It was absolute junk - completely unusable. It overloaded the RAM and CPU resources on my server, even without any remote connection. But RDP tools worked great. I had tried VNC a few times over the years and it's always been junk. But I was really surprised at how bad it worked on Linux.

just a passing by comment ..

VNC is still very much alive yes !

I don't need it for iPad, but use it elsewhere, it is great when all the fancy stuff fails

Thank you, I found your post helpful when I encountered this issue myself (unlike many of the comments on this post ranting about "junk tech").