Every time I force quit an application from Activity Monitor, I get a pop-up saying "You have forced to quit. Click Report to see from detailed information and sent a report to Apple.". It gives me the option to Ignore or Report. Is there a way to stop getting this notification altogether? In System Preferences > Security & Privacy > Privacy > Diagnostics & Usage I already have everything unchecked. I found this on the web and also tried writing this on the terminal > defaults write com.apple.CrashReporter DialogType none But this didn't help either. > You have forced Photos to quit. > > Click Report to see more detailed information and send a report to Apple. > > Ignore | Report...

The app icons in the "Force Quit" window are displaying incorrectly. I have seen this issue on various macOS versions, including Monterey, Big Sur, Catalina, and Mojave: I have reset my MacBook to the factory settings (Erased) and reinstalled macOS again, and I did an NVRAM reset as well, but the issue still persists! Here is a screenshot of my "Force Quit": Why are the app icons in the "Force Quit" window displaying incorrectly?

I would like to accomplish the simple task of making a 'button' (folder, executable, alias, etc.) open the Force Quit dialog box, on my mac. This button would ideally sit in the dock. On windows, this is easy, but I am having quite a bit of trouble making this here. So far I have tried several ways to do this, with two main methods. **Open the 'App' for Force Quit.** >This does not seem to exist as a standalone app, when I searched my system applications folders. **Somehow convert the keyboard shortcut for the Force Quit Dialog into an executable of sorts. I tried to do this using:** >Terminal - Using 'nano' based on (https://siytek.com/macos-terminal-command-as-a-shortcut/) I could not find the proper syntax to run a shortcut in the terminal. I am almost certain this is the way to do it, but I just can't find the proper syntax. >Apple Shortcuts App - Would not allow for a keyboard shortcut to be set as an input. >Various 3rd party software, HotKey and iCanHazShortcut - These were for the inverse of turning a 'button' into a shortcut. I know it's not typical to try to make more 'buttons' and less keyboard shortcuts, but in my case this is what is needed. Why? I work with software from almost every industry, and as a result I really have to think about organising files and apps. I have so far managed to put all my important apps and files into my dock, with only two complications, one being once I open an app, it appears in the dock, and the second being this. I like to have easy access to the force quit dialog to make sure I do proper memory management. I appreciate any help or advice.

Last Friday I updated my MacBook Pro (16", Nov '23) to macOS Sequoia (15.0). The OS language is English, but since the update, the body of the Force Quit Applications dialog is in Dutch: My region is set to The Netherlands, but even if I change that to United Kingdom, the issue persists. How can I change this behaviour? It looks similar to [this very old issue](https://discussions.apple.com/thread/7074197) but I never had Dutch configured in my system, and in that screenshot the dialog title is also translated. I noticed it appears on the log out dialog and log in screen as well: It might be related to the machine being set up by our company's help desk. I have removed that user, but the problem still persists.

Running Big Sur, v11.7.4, fully up to date, on a MacBook Air, Early 2014, as a Standard user (with known Admin credentials). I did recently install an update to Big Sur maybe a few days ago, but as I haven't recently installed any new apps, I can't be sure when this problem started or if it has anything to do with the update. # The Problem Begins I was trying to transfer some files to an Android phone so I launched the app *Android File Transfer* which was already installed on my computer. The app launched immediately but it wasn't seeing my phone. I hadn't used *Android File Transfer* in over a year, or more, so I thought I'd rule out an app issue by downloading the latest version of and updating the current version. That took me all of two minutes. I overwrote the current version with the new download and tried to launch it... and it just started bouncing in the dock... forever. What's even weirder is that after double-checking, I realized that the "new" version I installed was the same as the already-installed version. I guess *Android File Transfer* hasn't updated in a while. But why was it starting fine before and now it won't start if it is the *exact same app and version*? I tried Force Closing and relaunching, I tried restarting the computer and relaunching, and I tried logging in directly as the Admin user, I tried completely uninstalling (Move to Trash) and then reinstalling the app: the app just won't start. I figured out another way to get done what I needed with my Android phone, so I left that aside since everything else was working fine, and I don't really use *Android File Transfer* much. # The Problem Continues Then today, I needed to consolidate two similar folders. I pulled up the already-installed app *Beyond Compare*. It opened immediately without any problems. The app launched immediately without any problems, but this is also an app that I again hadn't used in a while, so again I decided to check for updates before continuing. It turns out I was on v4.3.7 build 25118 and v4.4.6 build 27371 was available on the website. I downloaded it from the website, extracted it, and then overwrote the existing install in the Applications folder... ...and now the app won't start. It's the exact same symptoms as above. It bounces forever in the Dock and never stops. I tried overwriting it again, I tried logging in as the admin user, I tried uninstalling (Move to Trash) and then reinstalling the app, and I even tried rolling back to the original version which started up just fine (v4.3.7). Nothing works: the app never starts, *not even the older version which had just launched with no problems minutes before*. # Help What the hell is going on and how can I go about troubleshooting/fixing this? I would try with updating another app, but now I'm a bit hesitant. So far both these apps are apps I rarely use. I don’t want to compromise an application I use daily. # Update **Edit 1:** So I experimented with another program I have installed: *IINA*. As I also have *VideoLAN* installed, I can get by if something goes wrong with *IINA* (which is also another great video player). I currently have *IINA* v1.3.1 installed, and it launches and works wonderfully. As the [*IINA* website states](https://iina.io/) , it requires macOS version 10.11 or higher to run, so there shouldn't be any problem with it running on Big Sur (11.7). I re-downloaded the DMG file for *IINA* v1.3.1 from their website and copied the app into my Applications directory, overwriting the current install. As predicted, I am getting the exact same behavior now. The app icon appears in the Dock, starts bouncing forever, and never successfully launches (whereas before it would launch quickly and without issue). Something is going wrong with my macOS when it writes new apps to the Applications directory. How do I figure out this problem? **Edit 2:** The problem is definitely related to the specific user profile. I created a brand new test profile, and I was able to launch all of the problematic programs with no problems. Something is happening on my main Standard user profile *only* when programs are installed (copied to the Applications folder) or updated (copied to and overwriting the existing app in the Applications folder). But that same new program or overwritten program will work just fine in the new user profile. What gives? What is unique to the user profile related to apps that could be causing this?

I have a Macbook 14" ( M1 Pro ) with 16GB of RAM. However, the Force Quit Applications window pops up when I surpass the ~10GB of RAM utilization. Even if I close some applications, this window keeps popping up after a short while. The system becomes unusable until I restart it. This mostly happens after 16-20h of uptime. Attached is the picture of htop output and the popup. I did not close any applications; I just waited for the popup to appear.

When I quit the Google Chrome web browser, it automatically reopens –– it won't stay closed! I tried quitting with Chrome –> Quit Google Chrome and Command-Q. How can I prevent Chrome from reopening when it quits? I searched on Ask Different and Stack Exchange, but I did not find any related questions. Jackson Short asked the question "Why does my Chrome browser keep restarting" on Chromebook Help. But his question refers to a Chromebook, and my question refers to Chrome for Mac.

The "Force Quit Applications" window opened spontaneously due to memory pressure. Now I can't close the "Force Quit Applications" window itself . The "X" button doesn't close the window and it doesn't have an icon in the dock or a menu bar.

I need to uninstall the "mate translate" app, but cannot stop it from the menu bar: the app has no menu when I select it. The app doesn't appear in "Force Quit" either. How can I stop it?

I'm on macOS Monterey and this is the system Force Quit menu: I know how to quit or kill an app from command line, either using osascript or kill / killall - but they don't do the exact same thing the system Force Quit menu does. Can I force quit an app using the same machanism the system Force Quit menu uses from command line?

Have had some problems from time to time on macOS 12.x where it hangs indefinitely. I'm working with Apple engineers on a resolution, but I'd like to figure out how to set up a method to send the equivalent of a sudo reboot to the kernel via a crazy key combination so that when apps and everything hang for hours on end I can break out of the situation more safely than just holding in the power button. Anyone see such a trick that still works for macOS 12?

I installed AnyTrans. I uninstalled it soon after. But, I can't seem to get my mac to stop running some helper that seems to somehow be leftover. I have tried: 1. going into activity monitor, selecting "AnyTransToolHelpers", clicking the "X" and selecting "Force Quit" 2. Restarting my computer In case this is any help, when I double-click "AnyTransToolHelpers" it opens a window and then I can select an "Open Files and Ports" tab which shows the following:

cwd
/
txt
/Users/myComputerName/Library/Application Support/com.imobie.AnyTrans/AnyTransToolHelpers.app/Contents/MacOS/AnyTransToolHelpers
txt
/Library/Preferences/Logging/.plist-cache.TWfVjDjS
txt
/usr/share/icu/icudt68l.dat
txt
/private/var/db/timezone/tz/2021a.3.0/icutz/icutz44l.dat
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/SystemAppearance.car
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/FauxVibrantDark.car
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/VibrantDark.car
txt
/private/var/db/analyticsd/events.whitelist
txt
/private/var/db/mds/messages/502/se_SecurityMessages
txt
/usr/lib/libobjc-trampolines.dylib
txt
/Users/myComputerName/Library/Caches/com.iMobie.AnyTransToolHelpers/Cache.db-shm
txt
/usr/lib/dyld
txt
/private/var/folders/k3/sjq7sq2n5wvfb3qwzkglwxr40000gp/0/com.apple.LaunchServices.dv/com.apple.LaunchServices-3027-v2.csstore
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/DarkAqua.car
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/Assets.car
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/FunctionRowAppearance.car
txt
/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources/Aqua.car
0
/dev/null
1
/dev/null
2
/dev/null
3
/Users/myComputerName/Library/Application Support/com.iMobie.AnyTransToolHelpers/AnyTransToolHelpers/LogsFolder/log-FD11C7.txt
4
/Users/myComputerName/Library/Caches/com.iMobie.AnyTransToolHelpers/Cache.db
5
/Users/myComputerName/Library/Caches/com.iMobie.AnyTransToolHelpers/Cache.db-wal
6
/Users/myComputerName/Library/Caches/com.iMobie.AnyTransToolHelpers/Cache.db-shm
7

**Is there any other way to get this AnyTransToolHelpers application to stop running?**

I was editing this file, and marking it up, highlighting etc, adding picture to it (as described in https://apple.stackexchange.com/questions/378888/add-images-to-existing-pdf-with-preview) , when suddenly Preview froze up and would not budge for a min or so. So I forced quit it, and then when I tried to open it again this error message shows up: > The file “...pdf” could not be opened. It may be damaged or use a file > format that Preview doesn’t recognise. Same message when opening in Adobe Reader app (which I downloaded to take a look to see if it's just a Preview issue). Did Preview corrupt my file? How can I get it back? It's pretty important for an exam and I don't have another annotated copy!!! Please help :(

my force quit window accidentally resized itself so it's wide. It's not taking up the whole screen but apparantally this is the least wide it can get. This it what it looks like right now It can't get any less wider than that, and I've seen it with my own eyes that the force quit window was smaller before. It may look like a small deal, but it really amplifies when you put yourself in my shoes. I use macos high sierra.

When I shutdown my computer I am having followin pop-up for X11, by default I want to always Quit instead of manually clicking. **[Q]** How to accept by defualt Quit for X11 when it is closed?

I've configured OSX to force all Finder windows to open in tabs - because this really takes care of all the clutter. The thing is, there's a shortcut to close all Finder windows, CMD+OPTION+W - and this will conveniently exit and quit all Finder windows completely. But this does not work for a window with multiple tabs. I've searched Stackexchange and Apple Forums high and dry, and I cannot find a solution. I'd be interested in ANY WAY to achieve this, an AppleScript, a keyboard shortcut...EVEN a third-party app. Any help would be appreciated, thanks.

My mac is in a weird state without particular reason. It is awake, but mouse clicks don't work, so I can't open any menus or apps. If I shut the lid, it locks after a while, but not immediately. When it gets to the locked state, it allows me to log into my account, by typing password, but it won't let me switch user or get to the screen, where I can restart it. Keyboard is even more weird. It react to all feature buttons (brightness, sound, keyboard brightness), except power button and "app buttons" (f3-f4). It doesn't react to holding power button for 10+ seconds, nor cmd+option+power button shortcut. I'm able to call "force quit apps" menu via cmd+alt+esc and close all apps and restart finder, but it doesn't help. Any ideas what should I do? I can't detach battery, since it 2015 retina model and I don't have correct screwdriver on me. UPDATE: External mouse and keyboard react the same way

I have a 2018 MacBook Pro with a Touchbar. Sometimes it will freeze up and I cannot access the Apple menu to run Force quit. Normally, you would be able to use Command+Option+Esc. However, the Command+Option+Esc method is not working for me. I'm thinking it may be because the Esc key is not a real key. I have no idea whether it is being registered. Is there any other way to issue a Force Quit without rebooting my system? PS. Making the Esc key a software-based key is not the smartest thing Apple could have done. **Update** In response to questions, one application that I am noticing this with the most is Audacity. I am processing a few hundred audio files using a macro. The macro is very simple: trim areas of silence, normalize, save as mp3. The script works perfectly on a Windows machine. Symptoms: Things just slow to a halt. I can move the mouse easily. But if I try to interact with anything on the Mac Desktop (through keyboard or mouse) things are very slow to respond. For example, just to open up Spotlight (Command-space) and type "terminal" takes about 10-15 minutes. Trying to open the Apple Menu it does not seem to respond (or maybe I'm just not waiting long enough).

I'm experiencing an unusual problem that is affecting many of the apps I use on a regular basis, including (but not limited to): Adobe Illustrator CC 2019, Sublime Text 3, FileZilla, and even Apple's native TextEdit! The sequence of events goes something like this: 1. An app freezes and I must Force Quit out of it. 2. I try to re-launch the app, but the icon just bounces in the Dock endlessly (until I Force Quit again) 3. I try to Shut Down the Mac, but macOS insists it can't shut down because said app is still running (although it shouldn't be, since I did a Force Quit). Also, no dot is shown below the app's Dock icon, leading one to believe it is not open, *but it's still running*. 4. I must physically hold the power button to shut down. ^ As you can see, the application is "Not Responding". But there is no dot below to indicate it is even open to begin with. I have tried to Force Quit the app(s) in question via Terminal as well, after identifying their Process IDs. Unfortunately, this has not worked either. Further Details -- macOS is the most current version to date: Mojave 10.14.2 This iMac shipped with High Sierra and I immediately updated it to Mojave before beginning to use it. This problem came to my attention after less than 1 month of use. I updated Mojave to 10.14.**2** hoping it would fix the problem, however the problem persists. The Mac is just over 2 months old. Freezing/hanging often often occurs upon saving a file. The file gets saved, but immediately after that the app (whichever app it is) becomes unusable. The problem seems to be closely tied to the file system. ^ It is usually right after saving a file that problems begin. This is a work machine, and one other employee at the company is experiencing the same issue with Mojave (on an older Mac). We both connect to the company LAN, and do Time Machine backups over the LAN. According to Disk Utility, nothing appears to be wrong with Macintosh HD: Running First Aid on “Macintosh HD” (disk2s1) NOTE: First Aid will temporarily lock the startup volume. Verifying file system. Volume could not be unmounted. Using live mode. Performing fsck_apfs -n -l -x /dev/rdisk2s1 Checking the container superblock. Checking the fusion superblock. Checking the EFI jumpstart record. Checking the space manager. Checking the space manager free queue trees. Checking the object map. Checking the Fusion data structures. Checking volume. Checking the APFS volume superblock. The volume Macintosh HD was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.230.6). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking snapshot 1 of 2. Checking snapshot 2 of 2. Checking the extent ref tree. Checking the fsroot tree. Verifying allocated space. Performing deferred repairs. The volume /dev/rdisk2s1 appears to be OK. File system check exit code is 0. Operation successful. Crash report comparison -- There's a lot of data to sort through, in crashes for multiple applications, so while it's hard to know what exactly to look for, the following lines look like they might provide a clue. I used Compare Side-By-Side in Sublime Text. Text highlighted in darker pink and darker green is dissimilar. Text highlighted in lighter pink and lighter green is similar. White text is identical. [![Crash log comparison showing a pattern with process diskarbitrationd ]] Here's more information from the log on the left side, which happens to be TextEdit, the third crash I experienced on 2019-01-29. I will include the portion for processes **diskarbitrationd ** and **diskimages-helper ** because there is a lot of correlation there with the FileZilla crash one day prior. Process: diskarbitrationd UUID: 6A57BB14-2FB6-3420-ABDA-429D1991CFE3 Path: /usr/libexec/diskarbitrationd Architecture: x86_64 Parent: launchd [1] UID: 0 Sudden Term: Tracked Footprint: 2016 KB Start time: 2019-01-29 09:26:56 +0900 End time: 2019-01-29 09:26:58 +0900 Num samples: 17 (1-17) Note: 1 idle work queue thread omitted Thread 0x252 DispatchQueue 1 17 samples (1-17) priority 31 (base 31) 17 start + 1 (libdyld.dylib + 93913) [0x7fff5cd86ed9] 1-17 17 ??? (diskarbitrationd + 29299) [0x10731d273] 1-17 17 ??? (diskarbitrationd + 31571) [0x10731db53] 1-17 17 CFRunLoopRun + 40 (CoreFoundation + 240468) [0x7fff2fb48b54] 1-17 17 CFRunLoopRunSpecific + 463 (CoreFoundation + 240968) [0x7fff2fb48d48] 1-17 17 __CFRunLoopRun + 1654 (CoreFoundation + 243217) [0x7fff2fb49611] 1-17 17 __CFRunLoopServiceMachPort + 337 (CoreFoundation + 245954) [0x7fff2fb4a0c2] 1-17 17 mach_msg_trap + 10 (libsystem_kernel.dylib + 4474) [0x7fff5cec017a] 1-17 *17 ipc_mqueue_receive_continue + 0 (kernel + 1651312) [0xffffff8000393270] 1-17 Binary Images: 0x107316000 - 0x10732efff diskarbitrationd (297.200.5) /usr/libexec/diskarbitrationd 0x7fff2fb0e000 - 0x7fff2ff5bfff com.apple.CoreFoundation 6.9 (1561) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff5cd70000 - 0x7fff5cd9ffff libdyld.dylib (640.2) /usr/lib/system/libdyld.dylib 0x7fff5cebf000 - 0x7fff5cee7fff libsystem_kernel.dylib (4903.231.4) /usr/lib/system/libsystem_kernel.dylib *0xffffff8000200000 - 0xffffff8000bfffff kernel (4903.231.4) /System/Library/Kernels/kernel Process: diskimages-helper UUID: 215C14BD-2ABA-36D8-AE6C-6279F4082D96 Path: /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/Resources/diskimages-helper Architecture: x86_64 Parent: launchd [1] Responsible: backupd UID: 0 Footprint: 4080 KB Start time: 2019-01-29 09:26:56 +0900 End time: 2019-01-29 09:26:58 +0900 Num samples: 17 (1-17) Note: 1 idle work queue thread omitted Thread 0x4f9a 17 samples (1-17) priority 20 (base 20) 17 1-17 17 mach_msg_trap + 10 (libsystem_kernel.dylib + 4474) [0x7fff5cec017a] 1-17 *17 ipc_mqueue_receive_continue + 0 (kernel + 1651312) [0xffffff8000393270] 1-17 Thread 0x4f9e 17 samples (1-17) priority 20 (base 20) 17 thread_start + 13 (libsystem_pthread.dylib + 9237) [0x7fff5cf79415] 1-17 17 _pthread_start + 70 (libsystem_pthread.dylib + 25199) [0x7fff5cf7d26f] 1-17 17 _pthread_body + 126 (libsystem_pthread.dylib + 13061) [0x7fff5cf7a305] 1-17 17 __NSThread__start__ + 1218 (Foundation + 73988) [0x7fff31ea5104] 1-17 17 ??? (diskimages-helper + 52345) [0x106fb1c79] 1-17 17 ??? (diskimages-helper + 55130) [0x106fb275a] 1-17 17 DI_kextDriveGetRequest + 43 (DiskImages + 114665) [0x7fff4537cfe9] 1-17 17 IOConnectCallStructMethod + 38 (IOKit + 34474) [0x7fff325906aa] 1-17 17 IOConnectCallMethod + 244 (IOKit + 32413) [0x7fff3258fe9d] 1-17 17 io_connect_method + 374 (IOKit + 32827) [0x7fff3259003b] 1-17 17 mach_msg_trap + 10 (libsystem_kernel.dylib + 4474) [0x7fff5cec017a] 1-17 *17 hndl_mach_scall64 + 22 (kernel + 1426566) [0xffffff800035c486] 1-17 *17 mach_call_munger64 + 555 (kernel + 2889483) [0xffffff80004c170b] 1-17 *17 mach_msg_overwrite_trap + 910 (kernel + 1717662) [0xffffff80003a359e] 1-17 *17 ipc_kmsg_send + 549 (kernel + 1633253) [0xffffff800038ebe5] 1-17 *17 ipc_kobject_server + 301 (kernel + 1786557) [0xffffff80003b42bd] 1-17 *17 ??? (kernel + 2706356) [0xffffff8000494bb4] 1-17 *17 is_io_connect_method + 527 (kernel + 8972575) [0xffffff8000a8e91f] 1-17 *17 IOUserClient::externalMethod(unsigned int, IOExternalMethodArguments*, IOExternalMethodDispatch*, OSObject*, void*) + 832 (kernel + 8934912) [0xffffff8000a85600] 1-17 *17 shim_io_connect_method_structureI_structureO + 460 (kernel + 8942556) [0xffffff8000a873dc] 1-17 *17 IOHDIXHDDriveOutKernelUserClient::getRequest64(HDIRequestOOL64 const*, HDIRequestOOL64*) + 257 (IOHDIXController + 11293) [0xffffff7f86529c1d] 1-17 *17 IOHDIXHDDriveOutKernel::getRequest(HDIRequestOOL64*, IOMemoryDescriptor*) + 31 (IOHDIXController + 7179) [0xffffff7f86528c0b] 1-17 *17 ??? (kernel + 1926025) [0xffffff80003d6389] 1-17 *17 thread_block_reason + 175 (kernel + 1876623) [0xffffff80003ca28f] 1-17 *17 ??? (kernel + 1881552) [0xffffff80003cb5d0] 1-17 *17 machine_switch_context + 195 (kernel + 2970867) [0xffffff80004d54f3] 1-17 Binary Images: 0x106fa5000 - 0x106ff2fff diskimages-helper (480.230.2) /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/Resources/diskimages-helper 0x7fff31e93000 - 0x7fff32261fff com.apple.Foundation 6.9 (1561) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff32588000 - 0x7fff3261afff com.apple.framework.IOKit 2.0.2 (1483.230.1) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff45361000 - 0x7fff45433fff com.apple.DiskImagesFramework 480.230.2 (480.230.2) /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0x7fff5cebf000 - 0x7fff5cee7fff libsystem_kernel.dylib (4903.231.4) /usr/lib/system/libsystem_kernel.dylib 0x7fff5cf77000 - 0x7fff5cf81fff libsystem_pthread.dylib (330.230.1) /usr/lib/system/libsystem_pthread.dylib *0xffffff7f86527000 - 0xffffff7f86532fff com.apple.driver.DiskImages 493.0.0 (493.0.0) /System/Library/Extensions/IOHDIXController.kext/Contents/MacOS/IOHDIXController *0xffffff8000200000 - 0xffffff8000bfffff kernel (4903.231.4) /System/Library/Kernels/kernel There are many other processes ending up like this: `` As follows are the processes that had dirty termination (while I don't understand exactly what that means, it doesn't sound good). Listed chronologically: ACCFinderSync authd com.apple.AmbientDisplayAgent com.apple.appkit.xpc.openAndSavePanelService com.apple.ctkpcscd com.apple.dock.extra coreaudiod corespotlightd CVMServer diskarbitrationd distnoted distnoted distnoted distnoted filecoordinationd fileproviderd Finder imklaunchagent IMRemoteURLConnectionAgent IMRemoteURLConnectionAgent IMRemoteURLConnectionAgent mds_stores nsurlsessiond nsurlsessiond nsurlstoraged opendirectoryd PAH_Extension pboard pkd rapportd securityd sharingd spindump symptomsd syslogd thermald useractivityd ViewBridgeAuxiliary WiFiProxy Update -- I have some good news, which is that **since turning off automatic Time Machine backups I have not had this problem!** But I still would like to know the cause of it, and if there's a way to still run scheduled Time Machine backups over the network without experiencing severe system problems. I can provide more details upon request.

I've scheduled a daily 1:00 AM shutdown of my MacBook but an app interrupts the process with a prompt that I need to manually answer before the shutdown can continue. How do I force an automatic override of this prompt or prevent it from appearing in the first place so the machine can shutdown successfully? The app in question is Audio HiJack on macOS - Sierra.