smb big sur

In OS X Catalina we were able to enable tokend using this command line: sudo defaults write /Library/Preferences/com.apple.security.smartcard Legacy -bool true Do you know if there a way to enable it in Big Sur? or the processes need to be changed to use CryptoTokenKit framework?

Hi, This question is about what would be the OS version number for MacOS Big Sur, I see two different versions 1.It shows as version 11 via About This Mac 2. When queried through sw_vers -productVersion it returns(SystemVersion.plist has it as 10.16) 10.16

Thank you Apple for a seriously lagging Big Sur. It's always a pleasure to up-downgrade performance. Just so you know... everything is slowed down: opening windows, searching, e-mail, opening apps... everything. Clicks are ignored sometimes and everything looks frozen, then after many seconds or tens of seconds multiple clicks are applied, and sometimes multiple instances open. It's almost funny. Painfully funny, because we need to do our jobs. But I am sure everything will be OK with the next big progressive upgrade, with fancy graphics and the shiniest lags possible. For the next OS, I dare to propose the name Captain Slow. Now that's some good (and free) copywriting. (iMac Retina 5K 2017 with fresh Big Sur 11.2.3)

I tried to install HP 5.1 drivers but Big Sur blocks the install

I have upgraded to Big Sur and installed Windows 10 via BootCamp. On the boot selection screen my choices are MacintoshHD and EFI Boot. On Catalina BootCamp, it was showing Windows instead of EFI Boot. Is this a bug?

Greeting fella Big Sur users! After the update I notice a HUGE difference between my previous (macOS Catalina) and latest (macOS Big Sur) battery drainage. My battery health lost 7 percentage immediately and the battery is draining 3x times faster than before. Example: I use the Preview all the time to open pdf files. I monitor my time on the MacBook and most of the time on 70 percent I had roughly 13:42 hours left. Now the (after the update) time reduced to 4 hours or so. I also compared battery drainage on both OS and Big Sur is eating a lot more on the same config. (2019 13 inch stock MacBook ) I'm looking forward to any suggestions or solutions!

I have a Retina display iMac from Sept. 2017 (I can't get it to come up, so am not sure) that came with the last Sierra install (or I'd get High Sierra but it was too buggy). Apple managed to get my spouse to take control of the computer and mangled it. It was fixed a couple months ago but now :start keeps rebooting obviously waiting for java to complete doing something (beach ball displays) - gets to about 3/4 rebooted; sits for 20 mins then flashes to the exact reboot point. Rinse and repeat from :start. Leave it to Apple to create something new after seeing this pattern for several reboots. After booting and rebooting several times, I got to the ID to sign in. Slow doesn't begin to describe what's going on. I know memory gets trounced with Big Sur it's why I didn't want that blasted OS. I've unplugged the mac from the back and the outlet for about 30 seconds and tried again. Help, please. This is beyond nuts. When these last computers die, I'll welcome the blue screen of death. Ran to App

Hello, I've run into an issue that for the newest macOS Big Sur 11.6.7 there is no Kernel Development Kit (KDK) available under: https://developer.apple.com/download/all/?q=kernel%20debug%20kit%2011.6.7 The latest possible KDK is for 11.6.5. However, the KDK's for 11.6.6 and 11.6.7 are missing. Could somebody please provide more information whether the missing KDK's will be avialable or not? It is necessary that the KDK matches the current kernel version, which means that using older KDK is not a solution. Best Regards abetz

Hi, I downgraded my MBP 15 mid-2014 from macos Big Sur to Mojave thanks to a backup installed by booting recovery mode. Everything was ok but now I can see an additional disk named Update ( my default disk is Macintosh HD ). Do I need this? Is everything ok like this? I've never seen this before. Also, I can notice that 8GB ( on 16GB ) of RAM is taken by App Memory ( I checked it with Memory Diag ) even when no app is open, just after booting my mac. I tried resetting SMC and PRAM but nothing worked for this. Can you help me? Thanks

Hi Guys, I have a issue with Big Sur beta is not booting. I tried to run fsck but it did not help. Tried to recover the disk but not working. Tried SUM but fsck -y is not available. I looked at the booting in verbose mode and seems like its stuck at below Kext com.apple.filesystems.smbfs not found for load from KC request tx_flush:1075 disk1 xid 39510 tx stats: 20 finish 20 enter 275 wait 0 0us close 1us flusg 3522us Any help is much appreciated. Thanks Kapil

Hi, I've been trying to benchmark certain algorithms on my M1 MBP with Big Sur. I've been using the open source memory_profiler application (https://github.com/pythonprofilers/memory_profiler) which on my machine uses the psutil library (https://github.com/giampaolo/psutil) under the hood. The psutil library uses an API for computing the resident memory of a process. Unfortunately, on Big Sur, the number returned by the API is far too large (Activity Monitor seems to provide an accurate measurement). The API used by psutil is described by https://opensource.apple.com/source/xnu/xnu-2050.7.9/bsd/kern/proc_info.c Under the hood, it calls proc_pidinfo. I've also tried using a mach API which seems to give an answer that is too low. #include mach/mach.h vm_size_t usedMemory(void) { struct task_basic_info info; mach_msg_type_number_t size = TASK_BASIC_INFO_COUNT; kern_return_t kerr = task_info(task_self(), TASK_BASIC_INFO, (task_info_t)&info, &size); return (kerr == KERN_

Many of my company's desktop applications support a method of deploying custom configurations if they're stored in the same directory as the installer to make deployments for smaller scale environments easier for system administrators. During install time, the installer looks for a particular file and copies it into place if it is there. As of Big Sur, however, we receive a new Operation not permitted when attempting to copy the file if the installer and the custom config are within a user account directory (e.g., /Users/<user>/Downloads). Example command that's reporting this error: install -o root -g wheel -m 0444 /Users/aUser/Desktop/my-custom-config.json /Library/Preferences/MyApp/my-custom-config.json This error doesn't occur if they're stored in a less protected area, like /Users/Shared. My suspicion is Big Sur has introduced a new protection against the installer scripts being able to access that location, but historically that's usually when a variation of the

In the release notes for Big Sur b4, we can find the same note as for b4: Updating to macOS Big Sur 11 beta from previous versions of macOS might take significantly longer than expected. What does significantly longer mean? 10 minutes ? 30 minutes ? 2 hours? From what I'm observing, updating from b3 to b4 is a bad as updating from b2 to b3. The Preparing macOS Big Sur beta X… step is taking an eternity to complete while the fans are spinning crazily. No processes are reported to use a lot of CPU time in Activity Monitor. Question: Do we need to erase the disk and install a fresh copy of Big Sur betas for each new beta?

I am trying to print an important tax document but the pdf is printing mirrored on mac Big Sur 11.2.3 Please help!