smb big sur

Hi There, I'm experiencing some frustration with Bug Sur and I wondered if this is something anyone else has experienced.. Essentially - I've noticed that when the battery goes below 10pc, it doesn't notify you. So, you can be working away in full screen (which I do, frequently) or in the middle of work calls and the Mac just dies. In Catalina a notification came up saying that your battery was low and to plug it in - but not Big Sur (yet) Please, put this back in - I don't want to have to keep checking my status bar all the time

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!!

Since the Mac Big Sur update it's impossible to connect my Caldigit dock for information the problem is with the network connection only because the 2sd screen plug on it is ok and when I connect the RJ45 directly with an Apple adapter I'm connected perfectly. alDigit say: CalDigit Support (UK)Unfortunately a lot of the previous issues that were present before on Catalina are still present on Big Sur at the moment. Our engineers initially confirmed that Big Sur beta 11 fixed a lot of issues and these were also confirmed on the Apple official forums but, since the launch version of 11.0, most of these changes have either been reverted or made worse. Our engineers haven’t been able to properly test Big Sur 11.0 release version at the moment due to current circumstances with California still on state wide lockdown and we haven’t been given approval from our head office to upgrade to the latest OS version here in the UK/EU at this moment in t

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:

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'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

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 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?

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

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.

Is /usr/libexec/java_home working on Big Sur for anyone? It won't output anything unless the JAVA_HOME environment variable is already set. When querying for the home folder for a specific version of the JDK, it always just returns the current value of the JAVA_HOME environment variable. Since the only useful purpose of the java_home tool is to get a value for setting JAVA_HOME, this is somewhat backwards and useless. I reported this against Big Sur betas but that didn't get anywhere. In one case I was actually told it was working as designed, which is clearly not the case.

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.

I updated to Big Sur this morning and Safari is almost unusable due to being super slow cleared cache, extensions. Doesn’t help any ideas?