Mar 22, 2016 A crash happens when a piece of software stops working altogether, and then closes on its own. In other words, the app quits when you did not tell it to. When this happens, you'll typically see a message noting that the application has 'unexpectedly quit” just as its windows disappears.
Jan 04, 2012 Most of my apps will not stay open once they're launched. All of the Apple apps work fine. The apps which don't seem to work are not terribly useful apps (games, ESPN Scores, Level, etc.). It's very strange. Can't figure out why this is happening. I haven't added any apps in the last few days and this just started (this badly) this evening. Jun 23, 2020 So the iPhone puts the app out of its misery and crashes it. You’ll need to do two things to clear things up. Double-press the home button to bring up the multi-task switching bar and then close all apps that are running in the background by swiping up each app. After this, try the app.
Are some or all of your Windows 10 apps not working properly? Previously, I wrote an article on how to fix the problem of missing Windows Store apps and recently I had a client who bought a Windows 10 machine to me where the Windows apps would appear to open, but then would close immediately.
If you are having this issue where an app fails to load, then it’s probably a permissions issue. There are lots of reasons why Store apps fail to start and one of them is because the permissions for certain Windows folders and registry settings have been changed, either manually or by group policy.
You can fix this problem by checking all the permissions for these folders and registry settings and making sure they are all correct. In this post, I’ll walk you through the steps for doing this so you can get your Store apps running again.
Windows 10 Event Log
You can confirm whether this is the cause of the issue by opening the event log and checking for the Event ID 5961 in the event log. You can open the event log by clicking on Start and typing in event log.
You’re going to have to navigate to the following log file to see if this particular event exists or not:
Once there, you’ll see a whole bunch of events listed there, probably thousands. You can’t really manually go through this, so click on the Find button at the very right and type in 5961. It’ll search through that log and if it finds anything, it will highlight that row. Double-click on the row and you should see some information like below:
If the event exists, you can be pretty certain that it’s a permissions issue for a new group in Windows called AllApplication Packages. What is All Application Packages? Well, it’s similar to the built-in Administrators or Users groups. All Application Packages includes any store app that is installed in Windows 10. If this group doesn’t have permissions to certain folders and registry settings, it will cause store apps to fail launching.
Fix File System Permissions
First, let’s fix the file system permissions. This is basically checking the permissions on three folders: Program Files, Windows and Users.
Go to Explorer and right-click on C:Windows and click on the Security tab. Here is what it should look like with the correct permissions.
If that is not what your permissions are showing for the directory, then click on the Advanced button at the bottom right. On the next dialog, click on the Change Permissions button.
You then want to click the Add button. Note that if the Add button is grayed out, it probably means the files are all owned by TrustedInstaller. Read my previous post on how to change permissions so that you can gain full control over the files and folders.
Here you need to click on Select a principal and then type in all application packages into the object name box. Make sure to click the Check Names button also before clicking OK.
Make sure the Type is set to Allow and Applies to is This folder, subfolders and files. Under permissions, make sure you have Read & execute, List folder contents and Read checked. Then click OK.
You’ll be brought back to the main permissions screen. Here you need to make sure to check the Replace all child object permission entries with inheritable permission entries from this object.
Once you have done this for the Windows directory, you need to do the same thing for C:Users and C:Program Files. For C:Users, everything is the same except you give the All Application Packages group Full Control. Also, if you’re running 64-bit Windows, you’ll need to do this for C:Program Files (x86) too.
Fixing Registry Permissions
For registry entries, open regedit by going to Start and typing in regedit. Once you have it opened, you need to check the permissions for HKEY_USERS. Right-click on HKEY_USERS and click on Permissions.
Make sure that All Application Packages has Read permission.
Now do the same thing for HKEY_CLASSES_ROOT. Next expand HKEY_LOCAL_MACHINE and do the check for HARDWARE, SAM, SOFTWARE and SYSTEM.
If you haven’t gone crazy by now, then congrats! The main issue that I saw with this whole process is changing the permissions on the system folders because you have to overcome TrustedInstaller in order to make changes to the permissions. Half the time that never works properly and then trying to get everything back to normal is just as risky.
You may be better off just resetting Windows 10, but it’ll require you to install all your third-party apps again. You can reset Windows 10 by going to Settings, click on Update & Security and then clicking on Recovery. If you’re trying to change permissions and running into errors, post a comment and we’ll try to help. Enjoy!
The Messages app makes sending and receiving iMessages on your Desktop a lot easier for Mac users. You don’t have to grab your phone just to send or reply to a message. Just open the Messages app, type your message, and send it just like how you do it on your phone.
Some Mac users, though, have encountered a critical error when opening the Messages app after updating to Mojave. The Messages app hangs or crashes after a Mojave upgrade, making it impossible for the users to read their messages or send a reply. Because of this error, the Messages app freezes, can’t sync, won’t load new messages, gets stuck in updating status, or won’t open at all.
This issue is usually accompanied by the following error message:
An internal Messages error occurred.
There was a problem with Messages. You need to quit and open Messages again.
However, quitting the app doesn’t help. Users who have encountered this error reported that the same message would appear every time they try to open the app. They have reported this error to Apple Support, and the team has acknowledged it as a bug related to Mojave. Some of them tried to downgrade to High Sierra and found no error when using the Messages app.
The engineers at Apple are already aware of the bug and are working on a patch to resolve the issue. There is no update, though, on when the official fix will be released. Instead of waiting for the official fix, you can use the solutions below to resolve this problem.
How to Fix Messages App Crashes After Mojave Update
If your Messages app freezes after a Mojave update, the first step you should do is to log out and quit the app completely. Force-quit Messages if necessary. Deleting your Mac’s junk files using Tweakbit MacRepair would make troubleshooting easier and faster. Next, reboot your Mac to refresh macOS before you start fixing the Messages app.
Fix #1: Log Out Then Log Back Into Your Messages App.
If you are able to open the messages app, log out of your account by clicking Messages at the top menu. From the dropdown menu, click Log Out. Close the app completely, then launch it again. Sign back in by clicking Messages > Log In. Your messages should be reloaded after signing in. Look around to see if everything is working fine. If you come across any problem, then jump to the other fixes below.
Fix #2: Check Your Date and Time Settings.
Incorrect date and time information may cause your Messages app to act up. Check your date and time settings to make sure they are consistent with your location, particularly after a major system update. There are instances when these settings are affected during the update, causing errors not only for the Messages app but other programs as well.
To check this: Random sampling software.
- Go to Apple menu > System Preferences > Date & Time.
- Click on the Time Zone tab.
- Tick off Set date and time automatically if the checkbox is unchecked.
- If it is, click on it to unselect the option. Wait for a few seconds before checking the box again.
- Enter your admin password if prompted.
After making sure that your computer has the correct date and time, restart your operating system and check whether the Messages app is back to normal.
Fix #3: Boot Into Safe Mode.
Temporary files, installation software, and other system caches might still be stored in your Mac after an update. Restarting in Safe Mode can help eliminate these unnecessary files that might be interfering with your Mac’s processes.
To boot into Safe Mode, follow these steps:
- Restart your Mac, then hold the Shift key immediately after you hear the startup sound.
- Release the Shift button when you see the login screen.
- Launch the Messages app while in Safe Mode and see if it’s working as it should.
Fix # 4: Delete Preferences, Cache, and Chat Database.
The Messages app stores information in various location on your Mac. All these files must be deleted, so your app can start from scratch and get rid of any errors that are plaguing it.
Messages App Crashing Mac
Canon lide 210 software download mac. To delete these files, follow the steps enumerated below:
- Close the Messages app.
- Open Finder and hold Options while clicking Go from the top menu. This should reveal the Library folder.
- Click Library, then search for the Preferences folder.
- Look for any of these .plist files:
- com.apple.imagent.plist
- com.apple.imessage.bag.plist
- com.apple.imservice.iMessage.plist
- com.apple.iChat.AIM.plist
- com.apple.iChat.Jabber.plist
- com.apple.iChat.plist
- com.apple.iChat.StatusMessages.plist
- com.apple.iChat.Yahoo.plist
- Back up these .plist files by copying them to the Desktop.
- Move all these .plist files to the Trash afterwards. This will clear previous settings and preferences of the Messages app.
- Go back to the Library folder and delete the following files:
- Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent
- Caches/com.apple.Messages
- Containers/com.apple.corerecents.recentsd
- Containers/com.apple.soagent
- Containers/com.apple.iChat/Data/Library/Caches
- IdentityServices
- Look for the Messages folder inside the Library directory and move the whole folder to the Trash.
- Next, launch Terminal by searching for it via Spotlight or going to Finder > Go > Utilities.
- Stop the IMDPersistenceAgent process by typing in this command: killall IMDPersistenceAgent.
- Type in this command in the console: rm -rf ~/Library/Caches/com.apple.Messages. This command should delete all cached data of the Messages app.
- To delete the chat database, enter this command in the Terminal window: rm -rf ~/Library/Messages.
- Enter this command to clear the preferences cache: killall cfprefsd.
Close everything and restart your Mac. Launch the Messages app to see if it is now working properly. Flutter 1.12 mac os app example.
Fix #5: Disable Messages in iCloud Settings.
Just like the iPhoto Library, Messages in iCloud ensures that all your messages are synchronized across all your devices. However, several users noted that the error seems to be caused by this feature.
To disable this feature on your Mac, follow the instructions below:
https://imevocci.tistory.com/11. My Mac is running OS 10.12.6.I did the three steps in your procedure but during the trash empty step, I got messages saying ‘Macintosh HD in us, SIP error message and ‘folder’ in use.Clicking the ‘Continue’ button each time I got a message (there were many backups I want to delete) continued the empty process but did not empty the trash.BTW: I then did use Time Machine to delete a, just one, backup from January 2017. However, ALL backups were deleted except the backups made today Aug. Certainly, using Disk Utility to erase the drive is faster than using the trash can to delete files.If you are okay with losing those backups and also confident that your Mac is not a risk at the moment of needing a backup, then erasing that TM drive and starting fresh is a good idea. How long it takes to create the new backup depends on how much data it needs to backup. Since it will be a copy of your entire system, the first backup will take at minimum a few hours and possibly even a few days.What we suggest, if possible, is using a different drive for your TM backup so you have the redundancy of the current TM drive if something happens while creating the new TM backup.Dave Williams says.
- Open Messages, then choose Messages from the top menu.
- Click on Preferences > Accounts.
- Choose iMessage from your list of accounts.
- Uncheck Enable Messages in iCloud.
- Choose either Disable All or Disable This Device.
Messages App Closes Immediately
Close Messages and re-open the app to see if this solution worked.
Final Thoughts
It can be annoying when the Messages app hangs or crashes after upgrading to Mojave because you can’t read or send messages on your Mac. However, dealing with a faulty built-in macOS app, such as Messages, can be tricky because you can’t just uninstall then re-install it. If you try moving Messages to the Trash, you’ll get an error message saying that you can’t uninstall the app because it is a critical part of the macOS system.
Instead of waiting for Apple to fix this bug, you can try the workarounds suggested above to get your Messages app working smoothly again.