Google Chrome won't open not launching nothing

The folder would be Google. if it doesn't exist, you could create a folder named Google in the ~/Library/Application Support folder. The ~ means the home directory for the account you are logged in to which gets translated to "/Users/<yourlogin>/. Bring up the Finder app with focus on the window, SHIFT+COMMAD+G, in the "Go to folder:" dialog box that pops up, put "~/Library/Application Support" without the double quotes. Create a Google folder if it doesn't exist. Right click on the Google folder and do "Get Info". Expand the "Sharing and Permissions" at the bottom. Click the lock in the bottom right to allow changes. Click the "+" in the bottom left to add another user, admin. Change the rights to Read & Write. Click the cog/gear and apply the changes.

I followed these steps too and it still didn't work. Next, I went to the google file I found under the ~/Library/Application Support and deleted it. I then went and deleted the Google found under applications and did a fresh install. It worked. My wife is so happy! Thank you for sending me in the right direction.

HERE IS WHAT WORKED FOR ME - I had to go one step more. From the Google folder, I had to command-i on Chrome and do the same - give read-write permissions to Admins (following the same steps as macdaddy outlines. Other things I was going to try was to remove any plists or any Google/Chrome folders and try launching again, but didn't need to.

Since I am getting this issue on new MacBook Airs I'm setting up for teachers, I have noticed a few more things...

If I simply remove the entire Google folder from the current user's Library/Application Support, then relaunch Chrome, it works fine. Since the user I'm signed into doesn't yet have anything in Google, no problem, but you may want to make a copy of the folders inside of Google before making that kind of drastic decision.

Additionally, once I logged out of the main (root?) user account (the account I used to set up the Mac), and had the user sign in with their network account, there was no trouble in their account, which it seems there would be since I'm only fixing Chrome in the user library, not the system library. I'd be curious to see if creating another account, and then launching Chrome in that new account would have the same issue. Also, after launching in the 2nd account, then going back to your original account, would anything change from doing that (in other words, would it help)?

I have more laptops I need to image and will see if I can verify that and get back to this forum.

You need to open Terminal (Spotlight search - type "terminal") and run the following command:

sudo rm -rf ~/Library/Application\ Support/Google/Chrome

In my case the issue was in the fact that 'root' was the owner user of the directory where Chrome is installed (BTW I see the same with Mozilla's directory) and therefore the account user didn't have the permission to start Chrome.

It was resolved by:

$ sudo chown -R <macAccountUserName> ~/Library/ApplicationSupport/Google

You'll be prompted to enter the Admin password at this point.

After that you can check the permission with the following command:

$ ls -lh ~/Library/ApplicationSupport

Search for the Google directory, you should see your username as the owner of the directory.

Start Chrome again. It will work.

Hope it helps others.

Regards,

This worked for me, but the fix doesn't necessarily need read/write privileges for admin. It just needs read/write for the individual users that will actually be using Chrome, which may be a bit safer?

I'd be nervous about granting any Google application admin write privileges!

You might want to consider starting a new discussion. Since this one is marked solved and is a couple of years old, less people are likely to look at it. A new post would be much more visible. You can link to this one.

Before starting your own discussion, try the below and post the results in the new discussion.

Try setting up another admin user account to see if the same problem continues. Please post back on whether or not this worked. Also try the Safe Mode. Please post back on whether or not this worked.

Isolating an issue by using another user account

Safe Mode - About

Safe Mode Startup – El Capitan. also Sierra

If it works in the Safe Mode, try running this program when booted normally and then copy and paste the output in a reply. The program was created by Etresoft, a frequent contributor. Please use copy and paste as screen shots can be hard to read. Click “Share Report” button in the toolbar, select “Copy to Clipboard” and then paste into a reply. This will show what is running on your computer. No personal information is shown.

Etrecheck – System Information

Just an updatate. I opened the package that contained the app and executed an installer that showed the details a command line environment. There I could see that it was a permission issue to create a folder and that the path I used before (root)/Library/Application Support/ actually existed but the right one was /Users/ldelabar/Library/Application Support/. After this I followed all the steps and it just worked fine!

Thank you!

Luis Felipe

Sona - you may want to verify that you are accessing your user library, not the Mac library. Make sure you are going to Finder>Go (on the menu bar)>then holding the option key, the Library folder will show up.

This was helpful and resolved the issue. The key is to provide read+write permissions on the "Google" directory located at~/Library/Application Support.

Thanks

Genius! This worked for me. I've been struggling with this for a while. Wasn't a problem on High Sierra but apparently it is with Mojave.

Thanks for the post.

a better approach to this would be to add your personal user account to the list and then give it read&write permissions since it is a personal folder (as indicated by it's location being prefaced by a tilde "~"). Unless there is a specific reason to do so personal folders should only be set to write enabled for the owner and potentially the system. Root and Admin can work around permissions anyway and other users should not have write access and probably not read either, that is the purpose of group folders.

Thanks - it's worked for me! I had to try about 3 times, but I hadn't followed your extremely helpful instructions to the letter

First time I hadn't got Chrome installed - I'd deleted it trying to reinstall...

Second time I didn't start from desktop

Tried this solution on macOS Mojave 10.14.6 and latest download of Chrome. Did not fix the problem. In my case I used Apple Migration Assistant to migrate from a MacBook Air running macOS Mojave 10.14.6 to a new MacBook Pro running macOS Mojave 10.14.6. Chrome still runs fine on the old MacBook Air, but it won't run on the new MacBook Pro. I suspect the bug here is with Migration Assistant.