Android Studio "Unable to save plugin settings"

All we need is an easy explanation of the problem, so here it is.

When I opened android studio today, it showed me the following errors:
Error 1

Error 2

Then, when after I restart Android Studio, I get these errors:
Error 3

After I enable “Android Support”, and restart, the first two errors show again, and when I restart again, I get this 3rd error again and the “Android Support” plugin is disabled again. (I even tried uninstalling and reinstalling Android Studio)

How can I fix this?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

I have solved this problem this way:-

  1. Go to File >> Invalidate caches/restart >> Invalidate and Restart
  2. After restarted, If warning comes just click on Enable Android Support

Method 2

I was using Gradle 4.1 and AS 3.0.1 when I got this error.

Look at Gradle console. If it looks anything like this, read on:

Plugin Error
Problems found loading plugins:
Plugin "Android Games" was not loaded: required plugin "Android Support" is disabled.
Plugin "Android NDK Support" was not loaded: required plugin "Android Support" is disabled.
Plugin "Android APK Support" was not loaded: required plugin "Android Support" is disabled.
Plugin "Google Developers Samples" was not loaded: required plugin "Android Support" is ...
Plugin "Fire... (show balloon)

Note that all say “required plugin Android Support is disabled.”

Also note the link “show balloon”.

  1. Click show balloon.

  2. Choose to enable Android Support.

  3. Restart AS.

I hope this helps you, too.

Method 3

This can happen if a module is not added correctly.

Instead of adding the module folder, adding the build.gradle results in a broken project and issues with the Android Support plugins.

To check if this is the issue, try creating a new Android project. If the new project can be open fine (may require enabling the plugins and restarting Android Studio), then it is a project issue.

If this is the case, delete the incorrect module from the project, and if required re-enable the plugins and restart Android Studio.

Method 4

I finally fixed it by removing .idea/workspace.xml and reenabling plugins worked.

Same issue happened to me when I installed AS 3.1 beta alongside AS 3.0.1(stable) and opened my project in it. It was ok for few sessions, until it wasn’t. Can’t figure out what exactly broke project configuration, but project would open in 3.0.1 and not in 3.1. Any other project would work on 3.1 too. Symptoms were the same: android support plugin is disabled, and it wouldn’t enable. I tried invalidating caches, reinstalling AS (even 3.1 stable version won’t work).
Eventually I noticed projectBackup and projectBackup2 folders created by studio in the project’s root folder. They contained versions of workspace.xml file. So I removed these backup folders, and workspace.xml from .idea folder. Then studio asked to reload project and that’s it – after that I could reenable all the plugins

Method 5

For my case this seems to be a rights issue. When starting Android Studio with admin rights no problems occur.

Re-enabling the plugins as admin and starting AS again with my default user does not help.


I updated to the latest canary.
With the admin user I’ve installed AS.
I completly removed .AndroidStudio/config, .AndroidStudio/system and .AndroidStudio/plugins beforehand (I use a different location for these files, so I have to replace after every installation. While doing this, I’ve noticed, that they renamed .AndroidStudio to AndroidStudio.2. That gave me the hint to remove those dirs.)
After this, I had no problems, regardless of which User ran AS.

Method 6

None of the single solutions above where sufficient for me. I had the same issue after updating from android studio 2.3.3 to 3.1.2.

  1. Close Android Studio
  2. Remove .idea/workspace.xml
  3. Restart android studio (your project with the issue is opened automatically)
  4. A new .idea/workspace.xml is created
  5. Sync project with gradle files
  6. Open File -> Settings – > Plugins -> Enable
    • “Android Support” Plugin.
    • Android NDK support (I had to disable and re-enable it)
  7. Restart Android Studio

Method 7

I got this error today, I updated the Android Studio from Help>CheckForUpdates>Update.
After that installed the missing Google Cloud plugins.
Now it is working fine.

Method 8

Got this problem recently with Android Studio 1.3 and 1.4.2 (beta). This was caused by an OutOfMemoryError in the Java heap.

I solved it by increasing the -Xmx and -XX:MaxPermSize values in the studio.vmoptions file

Method 9

In android studio Go to file->settings->plugin-> enable androidsupport

Method 10

In my case, I am using Ubunto and I had to Unlock the Folder of my project:
type this command on Terminal:

sudo chown -R $USER: $HOME

Method 11

You can try this:

Rename the folder where the project is in
Open the project in Android Studio (now you’ll have to browse for it)
Wait until it’s synced and close the project
Rename the folder back to original
That solved it for me. Just deleting the idea folder and invalidating caches did not solve the problem.

Method 12

If you are getting “Unable to save plugin settings” or “unable to save settings” Error window,

and you have tried all of the other solutions listed here, but they don’t work for you, try the following:

  1. Invalidate Cache: but don’t select restart yet, select just “invalidate”.
  2. Close project and then exit Studio
  3. If you have a previous backup of your Settings folder, restore it now.
    If not, you will need to Delete your settings folder. For example, in Windows:

/ < USER_HOME_DIR >/.AndroidStudioPreview3.2

or on Mac :

  1. Delete the .idea folder for your project
  2. Re-launch Android studio, but this time select import project

Android Studio will re-index your project, but now the error will be gone.
After Android Studio has completed a Gradle Sync, it’s probably a good idea to also make a backup of the settings folder

Method 13

In my case, I installed a plugin, and on an android restart, it was failing to start. This was causing the plugin workflow to not run completely, and give the above error.

Disabling the faulty plugin solved the issue.

Method 14

I just replace the project build.gradle like below. And it works.

    buildscript {
    repositories {
        maven{ url ''}
        maven { url "" }
        mavenCentral() // jcenter() works as well because it pulls from Maven Central
        maven {
            url ''
            name 'Google'

    allprojects {
    repositories {
        maven{ url ''}
        maven { url "" }
        mavenCentral() // jcenter() works as well because it pulls from Maven Central
        maven {
            url ''
            name 'Google'

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply