smb big sur

iMac Pro is crashing all the time. I have reset pram, clean install of Big Sur and all the hard drive sleep settings and key combination resets. This thing was crashing during sleep, now it is doing it while I am working. I left Windows for the stability of macOS did Bill pop in and start managing your engineering department? Anyone have a fix for this? panic(cpu 2 caller 0xffffff801d3eba25): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds service: com.apple.logd, total successful checkins since load (6490 seconds ago): 650, last successful checkin: 0 seconds ago service: com.apple.WindowServer, total successful checkins since load (6460 seconds ago): 623, last successful checkin: 120 seconds ago service: com.apple.remoted, total successful checkins since load (6490 seconds ago): 648, last successful checkin: 0 seconds ago Big Sur 11.3.1 (macOS Millennium Edition) Model Name: iMac Pro Model Identifier: iMacPro1,1 Processor Name:

Printer failed with update from Catalina to Big Sur. Removed printer/scanner Canon MG3060 from system, installed 'recommended' driver updates. Added printer back. Scanner functions perfectly, printer just 'hangs' telling me it is 'printing' but it does not. WiFi connection is fine, or of course the scanner wouldn't work. Frustrated beyond belief.

I have written a macOS app that uses the iTunesLibrary framework. The app utilizes the media item's persistentID as provided by the iTunesLibrary framework to manage the settings for the track within my app. I develop this app on an iMac (late 2015) using Xcode 12.4. I then distribute the app to my MacBook Air (2020 M1). I use Rsync to synchronize any music files from the Music Library that have been modified (lyrics/cover art, etc.), including the Music/Music/Music Library.musiclibrary database. The need for the persistentID of the media item to remain consistent from one machine to the other is paramount for the app to work. Otherwise, the app is broken. This is why I am Rsyncing the library database. I did not have an issue with this on macOS Big Sur 11.1 and earlier. The persistentID was being preserved on both machines and the software worked perfectly. However, for some reason now the persistentID is not being persistent across machines. It is like the Music database on the Macbook Air

I have a problem mounting an encrypted volume on Big Sur (11.1). In DiskUtility, when I select the volume, click Mount, enter password and click Unlock, nothing happens. I also tried to use CLI to unlock the volume using command: diskutil apfs unlockVolume /dev/disk1s6 but it gives me error: Passphrase: ACM: LibCall_ACMContextCreate: returning, err = -536870181. Error -536870181 (0xe00002db) creating ACM Context for passphrase I also tried to create a new encrypted volume with simple password '123', but after I unmounted it and tried to mount again I got the same error. Device: MacBook Pro (16-inch, 2019) Is it a bug in Big Sur or am I doing something wrong? Should I just wait for an update with a fix? I don't have an urgent need to decrypt the data because I have a backup. The question is about possibility of using encrypted volumes in macOS.

So after updating to Big Sur, my airpods won't connect to my Macbook. It let's me connect but after 5-10 seconds it just disconnects. (No audio can play during this time either). I've tried removing the airpods from my iCloud devices a couple ways but it didn't seem to make a difference. Please help!

I'm currently running MacOS Big Sur 11.0.1 on a MacBook Pro 16in and I'm trying to update to version 11.1 but I have been stuck on Preparing macOS Big Sur 11.1 Update... About 10 minutes remaining for a few hours. I have tried restarting my MacBook Pro multiple times but I keep running into the same problem. Please help!!

I've been attempting to download the macOS big sur beta for the past little while and it kept coming up with an issue on the installer where it said my Macintosh HD needed 34 more gigs of space. I cleared some unused files. FAR MORE THAN 34 GIGS. and the same error came up saying i still had the same amount of space open. I need help either updating the HD status on the big sur installer

Hi, Since updating to Big Sur i've had this strange error, that i've been debugging to try and help out a bit with this error i'm getting with local DNS. I use Docker/Kubernetes locally to run a particular application at a series of particular domains via the browser. I do this by adding local IPs to the Network/(Adapter)/DNS/DNS Servers and having the last item be 8.8.8.8 so it would pick up the local docker container DNS first and fall back etc. Upon upgrading (from Catalina) I noticed that these were not working. so did the normal things of flushing DNS, clearing cache etc. Then it would work, but only for a small period of time after a DNS flush using: sudo killall -HUP mDNSResponder So i would have a small window where i could access these, and once on the domain it seemed to be fine and would stick the DNS to the correct DNS Server IP, however all other local domains would fail, but if i run the flush DNS command again it would allow me onto the failed domain again. I naturally debugge

After updating to iOS Big Sur I can not share my screen when I'm using Zhumu. I'm an online English tutor so I need to have this function working.

I have a 21.5 inch iMac that is part of the Beta program but I have yet to receive the Mac OS Big Sur Beta Download. Each time I attempt to do so, I receive a message that the version is not available and a warning that a Time Machine backup can not be found- even though it successfully backs up every hour. I am currently working on MacOC Catalina 10.15.7 Any Suggestions?

Has anyone else got this issue? I've submitted it to Apple under FB7820658. Whenever I open System Preferences and click any pane icon (Desktop & Screensaver, General, etc), the app hangs for a second and then presents me with a window titled “System Preferences Internal Error”. When macOS Big Sur was first released as a developer beta, I installed it to a separate APFS volume first. I could use System Preferences fine there. I then booted back into macOS Catalina, deleted the Big Sur volume, and installed Big Sur over Catalina, keeping all of my data. System Preferences worked fine in Catalina. The error describes “NSPrefPaneBundle supportedAppearance” - due to “Appearance” my first thought was to toggle Dark Mode from Control Centre, but that did not fix anything. I’ve restarted many times and continue to have this issue.

I am having a problem after updating to Big Sur. I cannot access my files, neither to those on the desktop nor in documents, after an update to Big Sur. When I check the HD usage through About this Mac Storage, I see that the files are there. It shows 66 GB is used (15 GB system, 51 GB Other). When clicking on manage storage, it lists all accessible files and then lists a folder name other 51 GB, but grayed out, not accessible.

I have an AppleScript which sets my preferences, in this case for Finder. Prior to Big Sur, I was able to select a checkbox to toggle with the following: tell checkbox Recents to if value is 1 then click However, in Big Sur, the name property of these particular checkboxes appears to be missing. The following script run with Script Editor shows the difference: tell application Finder activate delay 1 end tell tell application System Events tell process Finder keystroke , using {command down} delay 1 tell window Finder Preferences click button Sidebar of toolbar 1 delay 0.5 tell checkbox 1 get properties end tell end tell end tell end tell Prior to Big Sur, the results are: {minimum value:missing value, orientation:missing value, position:{47, 943}, class:checkbox, accessibility description:missing value, role description:checkbox, focused:false, title:Recents, size:{297, 18}, help:missing value, entire contents:{}, enabled:true, maximum value:missing value

In updating to beta 4, Big Sur seems to have locked the drive with FileVault. It is trying to retry the update, but says my drive is encrypted and to enter the password. Problem is, my admin user password doesn’t work and neither does my iCloud password. I’ve tried terminal tricks from the recovery partition for hours with no success. I 100% did not set a FileVault password at any time manually, and this isn’t a case of a forgotten password on my admin account - I’m sure of it. It’s the same one I’ve used on my Mac for years and I’ve entered it with success hundreds of times in Big Sur before this update bricked my install. When I go to unlock my other partition, Catalina, it allows me to choose an associated user - my admin account. Big Sur drive does not even give me that option.

After installing macOS Big Sur Beta 3, the OS has started crashing many times per day. It appears that the following may be causing the issues: Safari Control Center WeatherWidget The Crash Reports are increasing in numbers. Next, restarting the machine isn’t an option because the system becomes unresponsive for me and must perform force shutdown. Thus, I’ll go back to Catalina for now and wait until the final release of macOS Big Sur in September or October of 2020.