Whenever I'm logged in as a certain user and trigger a shutdown or restart, I get prompted to enable FileVault. - I have searched everywhere to find the hook that causes this prompt, but I can't find it. - I've searched all the LaunchDaemon and LaunchAgent directories I can find. - I've reviewed the output of launchctl find. - I've done other things in the past as well but I don't remember them all. - I have upgraded my computer and transferred my user account multiple times since this started happening. It seems to stick to my user account. - I believe this might have come from Symantec Endpoint Encryption that was installed by my employer many years ago. But I've also tried all the uninstaller techniques I can find for that. It appears after all the desktop stuff has gone away. Any ideas for where else I can look for a hook that might trigger this? Update: **FileVault** is not currently enabled on the disk and I do not want to enable it. ![Screenshot of the FileVault dialog box saying 'To add this user to FileVault, enter the password for 'cquenell.'' ][1]

What does shutdown error code -59 on Macbook air mean? I can't find this specific code anywhere online

I'm asking for the opposite of https://apple.stackexchange.com/q/98416 , which requests a way to ensure that unkillable processes are eventually SIGKILL'd [\[3\]] (like SystemD's TimeoutSec ). To compare: 1. On NT-based Windows 11, sudo shutdown /r /fw /t 0 (yes, that's Windows sudo) is the sole official way to reboot to the EFI UI. This invokes the standard shutdown method (that its DotNet APIs would). 1. However, on Linux-based OSes, multiple methods may exist. As an example: 1. All include reboot, alongside their initialisation system's method (SystemD's systemctl reboot --firmware-setup [\[1\]] or OpenRC's loginctl reboot --firmware-setup, [\[2\]] etcetera). 1. However, KDE advises busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager SetRebootToFirmwareSetup b true && qdbus-qt6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logoutAndReboot, so that the DE gracefully shuts down its first-party applications. I'm aware that Apple, on its own platforms, tends to design its applications differently to 3rd-parties, and OS design frequently necessitates this. Consequently, is macOS like Windows, in that it solely exposes one way to shut down the OS via the CLI, or does a more graceful manner (that SIGTERMs) exist than merely reboot? [\[1\]]: https://superuser.com/revisions/1083166/1#content:~:text=setup%20menu%20using:-,systemctl%20reboot%20%2D%2Dfirmware%2Dsetup,-Documentation:%20https://www.freedesktop.org/software/systemd/man/systemctl.html%23%2D%2Dfirmware%2Dsetup [\[2\]]: https://github.com/OpenRC/openrc/issues/539#issuecomment-2203036622:~:text=OpenRC%20uses%20elogind:-,loginctl%20reboot%20%2D%2Dfirmware%2Dsetup,-so%20I%20shall [\[3\]]: https://stackoverflow.com/revisions/690631/6#:~:text=SIGKILL%20is%20used%20to%20forcefully%20remove%20the%20process%20from%20the%20kernel.%20It%20is%20special%20in%20the%20sense%20that%20it 's%20not%20actually%20a%20signal%20to%20the%20process%20but%20rather%20gets%20interpreted%20by%20the%20kernel%20directly.

My 10 days old MacBook Air M1 laptop is behaving abnormally i.e it's Keyboard Backlit light turns ON after I Shutdown my laptop or put it on sleep. The light starts flashing or becomes still. And when I turn MacBook On it becomes normal just like before. Currently it is running on BigSur 11.5.2 I have also went to system preferences. I have tried Diagnostics test but no issue was found.

I am looking to shutdown iMac computers triggered by an external/other system. Its for a fully automated internet cafe, to include iMac's where the "central automation software" can trigger a shutdown of the iMac if the paid time is consumed. With windows/intel PC's it is possible to trigger a shutdown of the PC from another system (cybercafe with a central managed system that triggers the shutdown when the time the customer paid for is fully consumed) My question is, if that is also possible for an iMac. If so, how ?

I have a MacBook Air 2017 with 8GB of RAM and 1.8 GHz Dual-Core Intel Core i5, After updating to macOS Catalina, while I’m using my laptop it would freeze and the screen would turn black with a folder sign with a question mark in the middle flashing. This happens a lot and when I reboot my laptop this message pops up: panic(cpu 2 caller 0xffffff7f87171ad5): userspace watchdog timeout: no successful checkins from com.apple.logd in 120 seconds service returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.drain-mem service: com.apple.logd, total successful checkins since load (830 seconds ago): 72, last successful checkin: 120 seconds ago service: com.apple.WindowServer, total successful checkins since load (800 seconds ago): 80, last successful checkin: 0 seconds ago Backtrace (CPU 2), Frame : Return Address 0xffffff912644b720 : 0xffffff800611a65d 0xffffff912644b770 : 0xffffff8006254a75 0xffffff912644b7b0 : 0xffffff80062465fe 0xffffff912644b800 : 0xffffff80060c0a40 0xffffff912644b820 : 0xffffff8006119d27 0xffffff912644b920 : 0xffffff800611a117 0xffffff912644b970 : 0xffffff80068c1ad8 0xffffff912644b9e0 : 0xffffff7f87171ad5 0xffffff912644b9f0 : 0xffffff7f871717fa 0xffffff912644ba10 : 0xffffff800685397e 0xffffff912644ba60 : 0xffffff7f87170cfe 0xffffff912644bb60 : 0xffffff800685cba3 0xffffff912644bca0 : 0xffffff80062035e2 0xffffff912644bdb0 : 0xffffff80061203c8 0xffffff912644be10 : 0xffffff80060f6d15 0xffffff912644be70 : 0xffffff800610db22 0xffffff912644bf00 : 0xffffff800622c065 0xffffff912644bfa0 : 0xffffff80060c1226 Kernel Extensions in backtrace: com.apple.driver.watchdog(1.0)[B6A95892-6C75-3CF5-A6CC-6D83F30FA1D5]@0xffffff7f87170000->0xffffff7f87178fff BSD process name corresponding to current thread: watchdogd Mac OS version: 19H2 Kernel version: Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 Kernel UUID: 05D51A3D-3A87-3FF0-98C3-9CF3827A3EDD Kernel slide: 0x0000000005e00000 Kernel text base: 0xffffff8006000000 __HIB text base: 0xffffff8005f00000 System model name: MacBookAir7,2 (Mac-937CB26E2E02BB01) System shutdown begun: NO Panic diags file available: YES (0x0) System uptime in nanoseconds: 838988891518 last loaded kext at 18297244763: org.virtualbox.kext.VBoxNetAdp 6.1.16 (addr 0xffffff7f89c9b000, size 28672) loaded kexts: org.virtualbox.kext.VBoxNetAdp 6.1.16 com.avast.PacketForwarder 2.1 org.virtualbox.kext.VBoxNetFlt 6.1.16 org.virtualbox.kext.VBoxUSB 6.1.16 com.avast.FileShield 4.0.0 org.virtualbox.kext.VBoxDrv 6.1.16 @fileutil 20.036.15 >AudioAUUC 1.70 >AGPM 111.4.4 >!APlatformEnabler 2.7.0d0 >X86PlatformShim 1.0.0 @filesystems.autofs 3.0 >!AHDAHardwareConfigDriver 283.15 >!AUpstreamUserClient 3.6.8 >!AHDA 283.15 >!AGraphicsDevicePolicy 5.2.6 @AGDCPluginDisplayMetrics 5.2.6 >!AHV 1 |IOUserEthernet 1.0.1 |IO!BSerialManager 7.0.6f7 >pmtelemetry 1 @Dont_Steal_Mac_OS_X 7.0.0 >!A!IBDWGraphics 14.0.7 >AGDCBacklightControl 5.2.6 >!A!ISlowAdaptiveClocking 4.0.0 >!ABacklight 180.3 >ACPI_SMC_PlatformPlugin 1.0.0 >!AMCCSControl 1.14 >!A!IBDWGraphicsFramebuffer 14.0.7 >!AFIVRDriver 4.1.0 >eficheck 1 >!AThunderboltIP 3.1.4 >!ACameraInterface 7.6.0 >!ALPC 3.1 >!ASMCLMU 212 |IO!BUSBDFU 7.0.6f7 |SCSITaskUserClient 422.120.3 >!U!SCoexistentDriver 489.120.1 >!UCardReader 489.120.1 >!ATopCaseHIDEventDriver 3430.1 >!AFileSystemDriver 3.0.1 >!AVirtIO 1.0 @filesystems.hfs.kext 522.100.5 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 @filesystems.apfs 1412.141.1 >!AAHCIPort 341.140.1 >AirPort.BrcmNIC 1400.1.1 @private.KextAudit 1.0 >!ASmartBatteryManager 161.0.0 >!ARTC 2.0 >!AACPIButtons 6.1 >!AHPET 1.8 >!ASMBIOS 2.1 >!AACPIEC 6.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 303 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 |IOUSBUserClient 900.4.2 @kext.triggers 1.0 >DspFuncLib 283.15 @kext.OSvKernDSPLib 529 >!AGraphicsControl 5.2.6 |IOAVB!F 850.1 @!AGPUWrangler 5.2.6 |IOSlowAdaptiveClocking!F 1.0.0 >!ABacklightExpert 1.1.0 |IONDRVSupport 576.1 >IOPlatformPluginLegacy 1.0.0 >!ASMBus!C 1.0.18d1 @!AGraphicsDeviceControl 5.2.6 |IOAccelerator!F2 438.7.3 >X86PlatformPlugin 1.0.0 >!AThunderboltEDMSink 4.2.3 >!AThunderboltDPOutAdapter 6.2.6 >IOPlatformPlugin!F 6.0.0d8 >!ASMBusPCI 1.0.14d1 >!AHDA!C 283.15 |IOGraphics!F 576.1 |IOHDA!F 283.15 @plugin.IOgPTPPlugin 840.3 |IOEthernetAVB!C 1.1.0 |Broadcom!BHost!CUSBTransport 7.0.6f7 |IO!BHost!CUSBTransport 7.0.6f7 |IO!BHost!CTransport 7.0.6f7 >usb.IOUSBHostHIDDevice 1.2 >usb.!UHub 1.2 |IOUSBMass!SClass 4.0.4 >usb.cdc 5.0.0 >usb.networking 5.0.0 >usb.!UHostCompositeDevice 1.2 >!AHS!BDriver 3430.1 >IO!BHIDDriver 7.0.6f7 |IO!B!F 7.0.6f7 |IO!BPacketLogger 7.0.6f7 >!AMultitouchDriver 3440.1 >!AInputDeviceSupport 3440.8 >!AHIDKeyboard 209 >!AHSSPIHIDDriver 59 |IOAudio!F 300.2 @vecLib.kext 1.2.0 |IOSerial!F 11 |IOSurface 269.11 @filesystems.hfs.encodings.kext 1 >!AXsanScheme 3 |IOAHCIBlock!S 316.100.5 |IOAHCI!F 290.0.1 >!AThunderboltDPInAdapter 6.2.6 >!AThunderboltDPAdapter!F 6.2.6 >!AThunderboltPCIDownAdapter 2.5.4 >!AThunderboltNHI 5.8.6 |IOThunderbolt!F 7.6.1 |IO80211!F 1200.12.2b1 >mDNSOffloadUserClient 1.0.1b8 >corecapture 1.0.4 |IOSkywalk!F 1 >!AHSSPISupport 59 >!A!ILpssSpi!C 3.0.60 >!A!ILpssGspi 3.0.60 >!A!ILpssDmac 3.0.60 >!A!ILpssI2C 3.0.60 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >usb.!UHostPacketFilter 1.0 |IOUSB!F 900.4.2 >!AEFINVRAM 2.1 >!AEFIRuntime 2.1 |IOSMBus!F 1.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >DiskImages 493.0.0 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!ASSE 1.0 >!AKeyStore 2 >!UTDM 489.120.1 |IOSCSIBlockCommandsDevice 422.120.3 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 |IOUSBMass!SDriver 157.140.1 |IOSCSIArchitectureModel!F 422.120.3 |IO!S!F 2.1 |IOUSBHost!F 1.2 >!UHostMergeProperties 1.2 >usb.!UCommon 1.0 >!ABusPower!C 1.0 |CoreAnalytics!F 1 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |IOReport!F 47 |IOTimeSync!F 840.3 |IONetworking!F 3.4 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.Libm 1 @kec.corecrypto 1.0 I have gone to apple and they wiped my laptop and reinstalled macOS Catalina but the problem still persists. What do I do?

I have a MacBook 7,1 (mid 2010) and sometimes it randomly shuts down. This only happens when I am doing something very resource intensive (like gaming). After the shutdown I can use my Mac for "normal" things without any issues, but as soon as I do the same thing as before the shutdown, it will shutdown again. When checking the console, it says "Previous shutdown cause: -102". The only thing I could find was "Overvoltage shutdown protection", but I wouldn't know why there would be an overvoltage. Disconnecting the charger and using the battery doesn't help. Resetting the SMC seems to help, but after a month or so the problem starts occurring again. I ran an Apple Hardware Test (both regular and extended version) and it doesn't find any issues. What can be causing this? Is it an issue with the motherboard? Just to make sure: Is it possible that it's the 6Gbps SSD (Samsung 860 EVO) that I installed (while my Mac officially only supports 3Gbps), somehow messing things up?

In macOS 14.0 and earlier, the shutdown command had a -u option for handling UPS-initiated emergency shutdowns. From the man page of shutdown on an old Mac: > -u The system is halted up until the point of removing system power, > but waits before removing power for 5 minutes so that an external > UPS (uninterruptible power supply) can forcibly remove power. This > simulates a dirty shutdown to permit a later automatic power on. OS > X uses this mode automatically with supported UPSs in emergency > shutdowns. On macOS 14.4 and later, this option was removed. In fact, Apple publishes the source code of the shutdown utility on GitHub , and commit 49dcc07 ("14.4") effectively removes all code that handles the -u option. Sure enough, by shutting down a machine running macOS 14.4 or later with command shutdown -uh now, the following message is printed to the console:

shutdown: -u has no effect

Anecdotally, I can say that I simulated a power loss on my UPS until my Mac mini (running macOS 15.1) automatically shut down. I waited for the UPS to completely run out of battery and, when I plugged it back in, the Mac mini did *not* restart, even if the "Start up automatically after a power failure" option is enabled in Settings. If my experience is confirmed, it means that Apple did not just remove the option to *manually* simulate a dirty shutdown, but they removed the feature entirely, even in the case of actual UPS-initiated shutdowns. How can we trigger a dirty shutdown on macOS 14.4 or later? As of now, it looks like there is no way of automatically restarting a desktop Mac after an emergency shutdown.

I have a problem with my MacBook Pro M1 Pro. I bought it in 2022, and now, when I type my password, it shuts down immediately and does not turn on again, even if I press the power button. For the MacBook to turn on again, I need to plug in the charger. This error always occurs the same way: after typing my password and pressing enter, the MacBook shuts down.

I have a problem with my iMac restarting when it should be shutting down. This doesn't happen all the time but appears to happen more frequently when I've had the computer on for a few hours. **What happens** 1. I shut the computer down via Apple Menu > Shut Down 2. The shut down cycle completes 3. The computer immediately reboots It doesn't behave like this https://apple.stackexchange.com/questions/102486/mac-os-x-never-shuts-down . The Mac responds to being shut down immediately. **Fixes I've tried** First I should state I've pulled out all USBs etc. The only wire in is the power cable. *Disk Utility* I've been in touch with Apple Support about this issue, and the only advice they could give was to run First Aid in the Disk Utility. Sometimes this allows me to shut down. Other times not. *Resetting the SMC* I've reset the SMC which doesn't help. This often leads to another issue which is freezing on reboot (Apple logo and progress bar that doesn't move). To fix this I reset the PRAM/VRAM *Reset the PRAM/VRAM* Resetting the PRAM allows me to shut down most of the time. Even then I have to do it 2 or 3 times before it works. *Complete reinstall/upgrade* I've also reinstalled the system twice, one time upgrading from El Capitan to Sierra. This has temporarily fixed the issue, but it soon comes back after a week or so. **Setup** iMac (27-inch, Late 2013) 3.4 GHz Intel Core i5 6 GB 1600 MHz DDR3 NVIDIA GeForce GTX 775M 2048 MB macOS Sierra 10.12.5 **EDIT:** Current Energy Saver Settings I'd really appreciate your help here guys, this has been going on a while and it's becoming a bit of a nuisance. **EDIT:** This question appears to highlight a pretty common occurrence. I'm happy to invest more into the bounty to get an answer that resolves or at least identifies the problem causing it to happen. **UPDATE:** After going through the steps in the answer provided by @monomeeth, Apple Diagnostics uncovered an error NDT001: There may be an issue with the Thunderbolt hardware. I've run Diagnostics before, but this time I ran it straight after the Mac restarted from a failed shut down. I'll be taking it into Apple for repair, so I'll keep this answer up to date with the outcome.

My Macbook Pro (Yosemite) early 2011 sometimes unexpectedly turns off when running heavy tasks on battery power. Is there a way to confirm this is because of overheating? Here's a part of system.log from the moment of shutdown. What other logs can I read? > Feb 24 08:22:56 macs-MacBook-Pro.local Skype: Failed to get > contents of directory "/Users/mac/Library/Logs/Skype". The file > “Skype” couldn’t be opened because there is no such file. Feb 24 > > 08:24:47 macs-MacBook-Pro systemstatsd: assertion failed: 14C109: > systemstatsd + 4269 [A886B71F-3A31-3324-9B30-5143FDF4ECCB]: 0xb Feb 24 > > 08:24:47 macs-MacBook-Pro com.apple.xpc.launchd > (com.apple.systemstatsd): Service exited with abnormal code: 1 > > Feb 24 08:54:10 localhost bootlog: BOOT_TIME 1424764450 0

I have an M1 Mac Mini that needs to auto-shutdown after 60 seconds on the UPS. We are using an APC Back-Ups 850VA model connected via USB. Also, this M1 mac mini has had its data migrated from a Time Machine backup of an Intel Mac Mini running OS X El Capitan 10.11.6. The mac properly recognizes the UPS and lists the UPS options in the Energy Saver preferences, however no matter what I set within the UPS settings, the UPS does not shutdown the machine. The only thing that does work is a warning when the Mac Mini is drawing from the UPS. **Does anyone have any suggestions? Nothing in the previous threads have worked.** Here are the relevant settings: **pmset -g** System-wide power settings: Currently in use: disksleep 10 powernap 1 womp 1 networkoversleep 0 sleep 0 (sleep prevented by coreaudiod, bluetoothd, powerd) Sleep On Power Button 1 ttyskeepawake 1 tcpkeepalive 1 autorestart 1 standby 0 **pmset -g ups** UPS settings: haltlevel on 100 haltafter on 1 haltremain on 15 **When UPS plugged in:** Now drawing from 'AC Power' -Back-UPS ES 850G2 FW:931.a10.D USB FW:a10 (id=25296896) 74%; charging present: true **When ups unplugged:** Now drawing from 'UPS Power' -Back-UPS ES 850G2 FW:931.a10.D USB FW:a10 (id=25296896) 74%; discharging; 4:14 remaining present: true

I have a system with normal user accounts and an account with "administrator" privileges. Whenever that admin account is logged in, normal users can not shut down the system any more. I need to enable this, with the understanding that this can cause an admin session to be unexpectedly terminated. How can I give normal users the power to force a shutdown (through the GUI) independent of whoever else is logged in at the time? The target environment is macOS Ventura, 13.x.

Is there any direct way (command line) someone could share, to recursively log into a file the voltage level of the battery? I just bought a new battery for my loyal macbook air (2012). After a few months of usage, it abruptly and randomly shuts off the laptop at 70% or less. Then it starts again as if nothing happened, but it can anytime randomly happen again–it did. With power cord everything is fine. I'm in contact with the battery manufacturer, they are quite old and reputed IMO (Kingsener), but I would like to gather some more info. Maybe a logger can detect a voltage drop right before it shuts off. This would also prove that the battery is interrupting the supply, instead of some hardware problem at my power management circuit or anything they could claim. I found this app that seems to draw graphics, but it is paid and I wouldn't like pay in these circumstances. https://www.bresink.com/osx/0BatteryMonitor/Docs-en/pgs/0040-Graphs.html Any other suggestions on the cause of the problem are welcomed! Reset SMC is done. Winter cold maybe? Greets, Domingo

This issue is with a Mac Pro (4,1; early 2009) running OS X 10.9.4 Mavericks. I have a strange problem, when I try to shutdown my Mac Pro. I get the grey screen with the activity indicator, but it does not shutdown, the indicator keeps spinning and spinning. I figured out how to run the Mac in verbose mode in order to locate the problem. So I think this is the relevant part from Console.app: 02.09.14 21:01:34,654 com.apple.launchd.peruser.502: (com.apple.PackageKit.InstallStatus) Throttling respawn: Will start in 10 seconds 02.09.14 21:01:34,700 WindowServer: CGXGetConnectionProperty: Invalid connection 52227 02.09.14 21:01:34,703 WindowServer: CGXGetConnectionProperty: Invalid connection 52227 02.09.14 21:01:34,703 WindowServer: CGXGetConnectionProperty: Invalid connection 52227 02.09.14 21:01:34,704 WindowServer: CGXGetConnectionProperty: Invalid connection 52227 02.09.14 21:01:34,704 WindowServer: CGXGetConnectionProperty: Invalid connection 52227 02.09.14 21:01:34,733 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,734 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,733 com.apple.launchd.peruser.502: (com.apple.universalaccessAuthWarn) Exited: Killed: 9 02.09.14 21:01:34,734 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,735 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,735 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,735 LaCie Network Assistant: windowWillClose 02.09.14 21:01:34,738 com.apple.launchd.peruser.502: (com.intego.commonservices.integomenu) Exited: Killed: 9 02.09.14 21:01:34,739 com.apple.launchd: (com.apple.ShareKitHelper) Exited: Killed: 9 02.09.14 21:01:34,742 NotificationCenter: Connection interrupted. 02.09.14 21:01:34,745 UserEventAgent: Captive: [UserAgentDied:142] User Agent @port=35335 Died 02.09.14 21:01:34,746 com.apple.launchd.peruser.502: (com.apple.iTunesHelper.108800) Exited with code: 1 02.09.14 21:01:34,748 com.apple.launchd.peruser.502: ([0x0-0x3a03a].com.apple.AppleSpell) Exited: Killed: 9 02.09.14 21:01:34,749 com.apple.launchd.peruser.502: (com.apple.ImageCaptureExtension2.26432) Exited: Killed: 9 02.09.14 21:01:34,756 com.apple.launchd.peruser.502: (com.apple.UserEventAgent-Aqua) Exited: Killed: 9 02.09.14 21:01:34,855 com.apple.launchd.peruser.502: (com.apple.gamed) Exited: Killed: 9 02.09.14 21:01:34,856 com.apple.launchd.peruser.502: (2BUA8C4S2C.com.agilebits.onepassword-osx-helper) Exited: Killed: 9 02.09.14 21:01:40,873 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:40,873 com.apple.kextd: Rescanning kernel extensions. 02.09.14 21:01:40,873 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:41,263 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:41,263 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:41,303 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:41,305 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,000 kernel: Resetting IOCatalogue. 02.09.14 21:01:42,111 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,113 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,195 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,195 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,202 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:42,205 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:44,767 loginwindow: ERROR | -[ApplicationManager quitPrivateProcesses] | Private process did not quit 02.09.14 21:01:44,823 sessionlogoutd: sessionlogoutd Launched 02.09.14 21:01:44,835 sessionlogoutd: DEAD_PROCESS: 89 console 02.09.14 21:01:44,840 loginwindow: ERROR | -[Application hardKill:] | Application hardKill returned -600 02.09.14 21:01:44,901 airportd: _doAutoJoin: Already associated to “FlooNetwork2”. Bailing on auto-join. 02.09.14 21:01:45,763 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:45,767 com.apple.kextd: Rescanning kernel extensions. 02.09.14 21:01:45,767 shutdown: halt by _spotlight: 02.09.14 21:01:45,000 kernel: Kext loading now disabled. 02.09.14 21:01:45,000 kernel: Kext unloading now disabled. 02.09.14 21:01:45,000 kernel: Kext autounloading now disabled. 02.09.14 21:01:45,000 kernel: Kernel requests now disabled. 02.09.14 21:01:45,767 shutdown: SHUTDOWN_TIME: 1409684505 767090 02.09.14 21:01:45,793 com.apple.kextd: Can't create kext cache under / - owner not root. 02.09.14 21:01:45,797 virusbarrierb: Unloading real-time scanner...

I was trying to install Microsoft Office 2011 when the installer hanged (and it is not going anywhere, I waited about 12 hours before trying to reboot this macbook). Now I can't restart this macbook until the installer finishes. Is there a easy way to locate what process is preventing my mac from restarting?

I use my iMac 2011 in Target Display Mode under High Sierra, to use it as an external display for my M1 MacBook Air from 2020. (works well, despite Apple websites say newer than 2019 is not supported). It has no keyboard, no mouse, and no internet connection - WIFI and BT turned off. On the iMac, I created a user that automagically logs in to MacOs. When I plug in DisplayPort cable to the laptop via a mDP 1.4 adapter, the Mac automatically switches into Target Display Mode. See picture for my DisplayPort adapter. What I would like is a way to shut down the iMac nicely, not a hard stop by holding the start button for N seconds. For example, on my Linux NUC, I can shut down smoothly by hitting the on/off button twice in a second. Can this be done on macOS (especially High Sierra) too?

I've recently started getting this error when running any of these commands on my iMac (macOS Ventura 13.5.2 (22G91)):

sudo pmset sched cancelall
pmset: Error 0xe00002bc scheduling repeating events

sudo pmset repeat shutdown MTWRFSU 01:00:00
pmset: Error 0xe00002bc cancelling all scheduled events

Interestingly, I've noticed that I can switch between sleep/shutdown but I can't cancel:

sudo pmset repeat shutdown MTWRFSU 01:00:00
pmset: Error 0xe00002bc scheduling repeating events

pmset -g sched
Repeating power events:
  shutdown at 1:00AM every day
# error, but shutdown is set 🤔

sudo pmset repeat sleep MTWRFSU 01:00:00
pmset: Error 0xe00002bc scheduling repeating events

pmset -g sched
Repeating power events:
  sleep at 1:00AM every day
# error, but it switched to sleep 🤔

sudo pmset sched cancelall
pmset: Error 0xe00002bc cancelling all scheduled events
pmset -g sched
Repeating power events:
  sleep at 1:00AM every day

# cancelling doesn't work 🤔

I've searched everywhere without luck. I don't see any relevant info on my /var/log/system.log and I've tried resetting the SMC, but the issue remains. Any ideas? Here's the output of my pmset -g assertions in case it's useful:

pmset -g assertions
2023-09-09 10:30:37 +0200
Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  1
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 156(bluetoothd): [0x0000081e0001885b] 00:00:20 PreventUserIdleSystemSleep named: "com.apple.BTStack"
   pid 745(sharingd): [0x0000061c000187e3] 00:08:54 PreventUserIdleSystemSleep named: "Handoff"
   pid 300(backupd): [0x00000188000185cd] 00:28:25 PreventUserIdleSystemSleep named: "Backup Job"
   pid 448(mdsync): [0x000005ab000b87d8] 00:10:46 BackgroundTask named: "com.apple.metadata.mds.scan"
   pid 106(powerd): [0x0000002b0008812b] 00:34:15 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
   pid 162(WindowServer): [0x00000065000981a8] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100000b78 service:AppleUserHIDEventService product:Karabiner DriverKit VirtualHIDKeyboard 1.6.0 eventType:3"
	Timeout will fire in 300 secs Action=TimeoutActionRelease
   pid 349(mds_stores): [0x00000039000b816a] 00:34:01 BackgroundTask named: "com.apple.metadata.mds_stores.power"
   pid 121(mds): [0x0000003f000b816b] 00:33:55 BackgroundTask named: "com.apple.metadata.mds.power"
Kernel Assertions: 0x4=USB
   id=503  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.00100000 owner=USB3.0 Hub
   id=505  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.00200000 owner=USB3.0 Hub
   id=506  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14400000 owner=USB 2.0 Hub [MTT]
   id=509  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14a00000 owner=Fast SSD
   id=510  level=255 0x4=USB creat=2023-09-09, 10:03 description=com.apple.usb.externaldevice.14900000 owner=Expansion Desk
   id=511  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14500000 owner=USB2.0 Hub
   id=512  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14b00000 owner=USB to PCIE Bridge
   id=514  level=255 0x4=USB creat=2023-09-09, 10:06 description=com.apple.usb.externaldevice.14200000 owner=USB2.0 Hub
   id=516  level=255 0x4=USB creat=2023-09-09, 10:07 description=com.apple.usb.externaldevice.14410000 owner=USB Advanced Audio Device
   id=517  level=255 0x4=USB creat=2023-09-09, 10:08 description=com.apple.usb.externaldevice.14470000 owner=USB 2.0 Hub
   id=519  level=255 0x4=USB creat=2023-09-09, 10:10 description=com.apple.usb.externaldevice.14420000 owner=Expansion Desk
   id=520  level=255 0x4=USB creat=2023-09-09, 09:55 description=com.apple.usb.externaldevice.14473000 owner=HD Pro Webcam C920
   id=521  level=255 0x4=USB creat=2023-09-09, 09:56 description=com.apple.usb.externaldevice.00110000 owner=USB3.0 Card Reader
   id=522  level=255 0x4=USB creat=2023-09-09, 09:56 description=com.apple.usb.externaldevice.00210000 owner=USB3.0 Card Reader
   id=523  level=255 0x4=USB creat=2023-09-09, 10:00 description=com.apple.usb.externaldevice.14240000 owner=USB 2.0 BILLBOARD
   id=524  level=255 0x4=USB creat=2023-09-09, 10:04 description=com.apple.usb.externaldevice.14540000 owner=USB 2.0 BILLBOARD
Idle sleep preventers: IODisplayWrangler

Would it be possible to list processes which block a shutdown of the Mac when finder is already killed? I want to resolve a different issue because I'm suspecting It's caused by a dangling process. https://apple.stackexchange.com/questions/462757/mac-does-not-shutdown-properly-after-update-to-macos-13-5

Since I updated 16” 2019 MacBookPro (i9) to macOS 13.5, it does not shut down properly. After a shutdown, the computer simply stays on, for example with the background image. If the shutdown is initiated from the login screen, it simply falls back to the login screen again. However, in the recovery mode the computer does shutdown properly; so it must have something to do with the Ventura update. I already tried reseting the SMC and NVRAM but no luck.