● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
MacBook Pro on a dark desk showing Time Machine not available error message in macOS Tahoe System Settings
Fix It Yourself · Troubleshooting

Time Machine not available Tahoe

Updated 6 August 202612 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Three separate customers hit this in the same week. Time Machine not available Tahoe 26.6, no useful error message, backups silently not running for days. The root causes vary but they're all fixable, and most don't require Terminal. This guide walks through every fix in order from quickest to most involved.

TL;DR

Time Machine not available Tahoe is caused by SMB protocol changes in Tahoe 26.x breaking NAS backups, non-ASCII characters in sparsebundle APFS volume names, or Tahoe blocking new HFS+ backup stores on Time Capsule. Fix NAS SMB settings first, then reset Time Machine preferences, then use Terminal for deeper SMB or sparsebundle issues.

⏱️ 13 min read ✅ 85% success rate 📅 Updated July 2026

Key Takeaways

  • Time Machine not available Tahoe most often comes from SMB compatibility issues between Tahoe 26.x and NAS devices
  • Non-ASCII characters in the internal APFS volume name inside a sparsebundle silently block backups
  • Tahoe will not create new backup stores on Time Capsule or HFS+ volumes; APFS is required for new setups
  • Resetting com.apple.TimeMachine.plist fixes corrupted preference state without touching your actual backup data
  • The /etc/nsmb.conf fix is the most reliable Terminal-level solution for persistent NAS SMB failures

At a Glance

  • Difficulty: Medium
  • Time Required: 15 to 30 mins
  • Success Rate: 85% of users

What Causes Time Machine Not Available Tahoe?

There isn't one single cause, which is part of what makes this frustrating. Tahoe 26.x introduced several changes that quietly broke Time Machine for a lot of people, and the error message 'not available' is about as helpful as a blank screen.

The biggest culprit is SMB. Tahoe changed its default SMB negotiation behaviour, and a lot of NAS devices (Synology, QNAP, older Buffalo units) don't match those new defaults. Time Machine needs specific SMB features to work: durable handles, SMB2 leases, and opportunistic locking. If any of those are off on the NAS side, Time Machine doesn't just slow down. It refuses to connect at all and shows 'not available'.

The second cause is a bit obscure. If your Mac's name or your NAS volume name contains non-ASCII characters (accented letters, Chinese, Japanese, Arabic, anything outside standard A to Z), the internal APFS volume inside your Time Machine sparsebundle may have been named with those characters. Tahoe silently fails when it encounters that. The backup gets stuck on 'Preparing backup' indefinitely, or just shows 'not available' without explanation.

Third: Tahoe made a policy change around HFS+ volumes. If you're using an older Time Capsule and trying to set up a fresh backup, Tahoe will block it. It won't create a new backup store on HFS+ at all. This isn't a bug exactly, it's intentional, but it catches people off guard. Existing backup stores created on earlier macOS versions can still be used, but new ones can't be created from Tahoe.

Finally, corrupted preferences. The file /Library/Preferences/com.apple.TimeMachine.plist stores destination configuration. If it gets corrupted (after an OS update, a hard shutdown mid-backup, or a failed migration), Time Machine loses track of its destinations entirely. Same goes for serverMarkers.plist, which handles network destination recognition. Both are fixable without touching your actual backup data.

Worth noting: Tahoe 26.4 had the worst of the network backup credential bugs. If you're still on 26.4, updating to 26.5 or 26.6 alone may fix things. Check System Settings > General > Software Update first before anything else.

Time Machine Not Available Tahoe: Quick Fix

Start here. This takes five minutes and sorts it for a decent chunk of people, especially if the issue is a transient credential glitch or a post-update configuration hiccup.

1

Reset Time Machine Destination Easy

  1. Open Time Machine settings
    Go to System Settings > General > Time Machine.
  2. Turn off automatic backups
    Toggle off 'Back Up Automatically'.
  3. Remove the backup disk
    Click the current backup destination and select 'Remove Disk' if the option appears.
  4. Re-add the same disk or share
    Click 'Add Backup Disk' and select your NAS share or external drive again. Re-enter credentials if prompted.
  5. Turn automatic backups back on and test
    Re-enable 'Back Up Automatically', then click 'Back Up Now'. Watch whether 'not available' disappears and the backup begins.
If the backup starts and shows a progress bar, you're sorted. Check System Settings > Time Machine the next day to confirm the 'Latest Backup' timestamp is updating.
If your NAS share isn't showing up at all when you try to re-add it, go to Finder > Go > Connect to Server and reconnect the share manually first. Then return to Time Machine settings.

For users who rely on a proper backup strategy, it's also worth considering dedicated backup clone software alongside Time Machine. Time Machine is good for incremental versioned backups, but a bootable clone gives you a separate recovery path if Tahoe's backup engine itself has issues. We'll flag where that fits in the workflow below.

More Time Machine Not Available Tahoe Solutions

If the quick reset didn't fix it, one of these two intermediate fixes almost certainly will. The NAS SMB settings fix in particular has a very high success rate for Tahoe users on Synology and QNAP hardware.

2

Fix NAS SMB Settings Medium

  1. Open your NAS control panel
    For Synology: log into DSM, go to Control Panel > File Services > SMB. For QNAP: go to Control Panel > Network & File Services > Win/Mac/NFS. Other brands have similar paths.
  2. Set SMB protocol version
    Set Maximum SMB protocol to SMB3. Minimum can stay at SMB2.
  3. Enable required features
    Turn on Opportunistic Locking, SMB2 Lease, and SMB Durable Handles. All three need to be active for Tahoe's Time Machine to connect properly. See Synology's official SMB settings documentation for exact option names on DSM.
  4. Disable server signing and transport encryption
    Set Server signing to No or Auto. Disable transport encryption if it's on. These add overhead that causes Tahoe's SMB client to time out during Time Machine's handshake.
  5. Save and restart SMB service
    Apply changes. Most NAS units restart the SMB service automatically on save.
  6. Reconnect the share and re-add in Time Machine
    In Finder, disconnect and reconnect the NAS share. Then go back to System Settings > Time Machine and re-add the destination. Run a manual backup.
This fix resolves the majority of Time Machine not available Tahoe cases on NAS hardware. If the backup starts progressing past 'Preparing backup', the SMB settings were the issue.
3

Reset Time Machine Preferences File Medium

  1. Turn off automatic backups
    System Settings > General > Time Machine > toggle off Back Up Automatically.
  2. Open the Preferences folder
    In Finder, press Cmd+Shift+G and enter: /Library/Preferences/
  3. Move the plist to Trash
    Find com.apple.TimeMachine.plist and drag it to Trash. Don't empty Trash yet in case you need to restore it.
  4. Reboot
    Restart the Mac. macOS will create a fresh preferences file on next launch.
  5. Reconfigure Time Machine
    Open System Settings > General > Time Machine and re-add your backup destination. Re-enter NAS credentials if needed.
After reconfiguring, run a manual backup. If it completes without showing 'not available', the preferences file was corrupted. You can now empty the Trash.
This is non-destructive. Deleting the plist doesn't touch your actual backup data on the disk or NAS. It only removes Time Machine's configuration, which you rebuild in the last step.

One thing that trips people up here: after a plist reset, Time Machine sometimes takes a few minutes to recognise a network destination. Give it two to three minutes before assuming it's failed again. Also, if you're on a Mac with a non-English system language, it's worth temporarily switching to English (US) in System Settings > Language and Region, rebooting, and testing again. It's a diagnostic step more than a permanent fix, but it helps isolate whether the language setting is contributing to the naming issue described in the advanced section below. This kind of configuration sensitivity is similar to what you'd see with other platform-specific bugs, like the Windows RE Image not found error, where system locale and regional settings quietly affect what the OS can and can't find.

Advanced Time Machine Not Available Tahoe Fixes

These take longer and require either Terminal or Disk Utility's more obscure features. But they fix the cases that nothing else touches.

4

Edit /etc/nsmb.conf to Fix SMB Negotiation Hard

  1. Open Terminal
    Applications > Utilities > Terminal, or Spotlight search for Terminal.
  2. Edit or create nsmb.conf
    Run: sudo nano /etc/nsmb.conf. Enter your admin password when prompted. If the file doesn't exist, nano will create it.
  3. Add the SMB tuning block
    Type or paste the following exactly:
    [default]
    signing_required=no
    protocol_vers_map=6
    streams=yes
    durable_handles=yes
    The value protocol_vers_map=6 tells macOS's SMB client to use SMB 2.x and 3.x (binary flags 2+4=6), which is what Tahoe's Time Machine expects.
  4. Save and exit
    Press Ctrl+O, then Enter to confirm the filename, then Ctrl+X to exit nano.
  5. Reboot and test
    Restart the Mac. Reconnect to the NAS share in Finder, then open Time Machine and run a manual backup.
If Time Machine starts backing up without the 'not available' message, the SMB negotiation was the root cause. This fix persists across reboots.
If you already have an /etc/nsmb.conf file with other settings, don't overwrite them. Add only the lines that aren't already present. Duplicate keys can cause unexpected behaviour.
5

Rename Non-ASCII APFS Volume Inside Sparsebundle Hard

  1. Stop Time Machine
    Turn off Back Up Automatically and wait for any in-progress backup to stop.
  2. Open Disk Utility
    Applications > Utilities > Disk Utility.
  3. Mount the sparsebundle
    In Disk Utility's menu bar, choose File > Open Disk Image. Navigate to your NAS share (it should be mounted in Finder already) and find the file named something like MacName.sparsebundle. Select it and click Open.
  4. Locate the internal APFS volume
    In Disk Utility's sidebar, you'll see a new volume appear under the sparsebundle. It may have a name with accented or non-Latin characters if your Mac name or NAS was set up in a non-English locale.
  5. Rename to ASCII-only
    Click the volume, then click the name field (or use the Info button). Rename it to something like TimeMachineBackup. No spaces, no accents, no special characters.
  6. Eject and test
    Right-click the volume in Disk Utility and choose Eject. Then go to Time Machine and run a manual backup.
The backup should now progress past 'Preparing backup' and complete normally. This is the fix for the silent failure that Tahoe introduced for non-ASCII volume names.
6

Time Capsule Workaround via Dual-Boot Sequoia Hard

  1. Understand the limitation
    Tahoe will not create a new HFS+ backup store on Time Capsule. This is intentional. But if the store already exists, Tahoe can continue using it.
  2. Install Sequoia in a separate APFS container
    Use Disk Utility to create a new APFS container on your Mac's internal drive (or an external drive). Install macOS Sequoia there. This is a full second OS install, not a virtual machine.
  3. Boot into Sequoia and set up Time Machine
    Hold Option at startup to select Sequoia. Open Time Machine in Sequoia and add your Time Capsule as the backup destination. Let it run the initial backup and create the HFS+ backup store.
  4. Reboot into Tahoe
    Once the initial store exists, boot back into Tahoe. Open System Settings > General > Time Machine and add the Time Capsule. Tahoe will detect the existing store and allow continued backups.
This is a proper workaround, not a quick fix. It's practical for users who already manage dual-boot setups. For most people, switching to an APFS-formatted external USB drive is a much simpler path forward. See Apple's guidance on Time Machine disk formats for what's officially supported in Tahoe.

One more thing worth mentioning for Tahoe 26.4 users specifically: the system logs (Console.app, search for 'TimeMachine') may show errors like NAConnectToServerSync failed with error: 80. That's the credential bug. The fix is either the serverMarkers.plist edit (Terminal, root access, careful plist editing, not for the faint-hearted) or simply updating to 26.5 or 26.6 where Apple patched it. Check System Settings > General > Software Update first. Keeping your system current is genuinely the single best preventive measure here. It's the same principle behind staying on top of updates for any platform-critical tool, whether that's macOS or something like a secure multi-platform notes app that depends on consistent OS-level encryption APIs.

Preventing Time Machine Not Available Tahoe

Most of these problems are avoidable. Here's what actually matters, in order of importance.

Format new backup disks as APFS. This is non-negotiable in Tahoe. HFS+ is dead for new Time Machine stores. If you're buying a new external drive for backups, format it APFS in Disk Utility before adding it to Time Machine. See Apple's Time Machine setup guide for the current recommended workflow.

Use ASCII-only names everywhere. Your Mac's computer name (System Settings > General > Sharing > Local Hostname), your NAS volume names, and any existing sparsebundle APFS volume names should all be plain ASCII. No accents, no special characters. This one catches people who set up their Mac in a non-English locale years ago and never thought about it again.

Stay updated past 26.4. The credential and network backup bugs were worst in Tahoe 26.4. Apple addressed them in subsequent point releases. If you're still on 26.4, update first and test before doing anything else.

Configure NAS SMB properly and leave it alone. Once you've set SMB3, durable handles, leases, and opportunistic locking on your NAS, don't let firmware updates reset those settings. Check them after any major NAS firmware update.

Check the backup timestamp regularly. Open System Settings > General > Time Machine and look at 'Latest Backup'. If it's more than 24 hours old and you haven't been away from home or the office, something's wrong. Tahoe can fail silently for days without any notification. Don't assume it's running just because you set it up once.

Keep enough free space on the backup destination. Time Machine needs room to store incremental snapshots. If the destination disk is over 90% full, backups start failing. Monitor it. This is a boring one but it's responsible for more 'not available' errors than most people realise.

Time Machine Not Available Tahoe: Summary

Time Machine not available Tahoe is a real and frustrating problem, but it's fixable in almost every case. Start with the basic reset and destination re-add. If that doesn't work, fix your NAS SMB settings (SMB3, durable handles, leases, no signing). If the backup still gets stuck on 'Preparing backup', check for non-ASCII characters in the sparsebundle APFS volume name and rename it. For persistent SMB issues, the /etc/nsmb.conf edit is the most reliable Terminal-level fix. Time Capsule users on a fresh Tahoe setup need the dual-boot workaround or a switch to an APFS external disk. And if you're still on 26.4, update first. That alone fixes a meaningful number of Time Machine not available Tahoe reports without any other intervention.

Quick Reference

  • Reset destination first (5 mins, no Terminal)
  • NAS SMB settings: SMB3, durable handles, leases, no signing
  • Non-ASCII sparsebundle volume name: rename via Disk Utility > Open Disk Image
  • Corrupted prefs: delete /Library/Preferences/com.apple.TimeMachine.plist and reboot
  • SMB negotiation: /etc/nsmb.conf with signing_required=no and protocol_vers_map=6
  • Time Capsule new setup: dual-boot Sequoia to create initial HFS+ store
  • Still on 26.4: update to 26.5 or 26.6 first

Frequently Asked Questions

Tahoe 26.x changed its SMB defaults in ways that break Time Machine specifically. Your NAS can serve files fine while still failing Time Machine's stricter requirements for durable handles, SMB leases, and opportunistic locking. Fix NAS SMB settings first.

Only if an existing backup store already exists on it from an earlier macOS version. Tahoe refuses to create new HFS+ backup stores on Time Capsule. For a brand-new setup you need an APFS-formatted external disk, or you can boot into Sequoia to initialise the store and then continue from Tahoe.

Usually either a non-ASCII character in the internal APFS volume name inside the sparsebundle, or an SMB negotiation failure with the NAS. Rename the APFS volume to ASCII-only characters via Disk Utility, or adjust NAS SMB settings to match Tahoe's expectations.

Always APFS for new disks. HFS+ is not supported for new Time Machine backup stores in Tahoe. If you have an old HFS+ backup from an earlier macOS version it may still work, but any fresh setup needs APFS.

Yes. The Tier 1 reset and Tier 2 NAS SMB settings fixes require no Terminal at all. Terminal only comes in for the /etc/nsmb.conf edit and the serverMarkers.plist workaround, both of which are Tier 3 last resorts.