You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: FAQ.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,6 +83,37 @@ See this [Cult of Mac report](https://www.cultofmac.com/news/macos-tahoe-26-4-br
83
83
84
84
**Workaround:** Macs running these versions can still use the device as a standard Samba network share in Finder, but Time Machine backups will not work properly. You can also try the workaround mentioned in the article.
85
85
86
+
#### If you have the OSStatus Error 80
87
+
88
+
OSStatus Error 80 can happen when macOS is trying to reuse an existing Time Machine backup and stale local backup state gets in the way.
89
+
90
+
Try these steps:
91
+
92
+
1. Make sure the Time Machine backup is not mounted or in use on any Mac.
93
+
2. In Finder, open the SMB share and find the affected `.sparsebundle`.
94
+
3. Right-click the `.sparsebundle`, choose "Show Package Contents", and delete the `lock` file if one is present.
95
+
4. Open Keychain Access and delete entries that reference the affected `.sparsebundle` or `.sparsebund` name, especially matching entries in the System keychain.
96
+
97
+
If Keychain Access cannot remove the entries, use Terminal to find and delete the matching generic password entries. Replace the example sparsebundle name with your real one:
If it still fails, check Keychain Access for older Time Machine entries that refer to the same Time Capsule or backup and remove only entries you recognize as related to this backup.
0 commit comments