Getting the following error in the admin in a Drupal 8 site:

The following module is missing from the file system ....

Looks like a custom module was enabled and deleted without disabling it.

How can I fix this error?

  • Are you using the configuration management in the site? – Adrian Cid Almaguer Sep 12 '17 at 20:06
  • Yes I am using that – Kevin Sep 12 '17 at 20:09
  • Some advance with the problem? I want to know at the end how do you solve the problem, this can arrive me too in any project. – Adrian Cid Almaguer Sep 15 '17 at 16:34

Assuming you have deleted an unimportant custom module which doesn't need any uninstall routine to be triggered you can use the following Drush command.


drush sql-query "DELETE from system where type = 'module' AND name = 'MYMODULE';"


drush sql-query "DELETE FROM key_value WHERE collection='system.schema' AND name='MYMODULE';"

See How to fix "The following module is missing from the file system..." warning messages for more info and alternatives.


If you have Drupal Console then a quick way to fix this is to generate a module with the same machine name, then uninstall it.

$ drupal generate:module

Then type the machine name at the appropriate prompt and accepts defaults for everything else.

$ drush pm-uninstall

Then you can delete the newly generated module from the file system and continue with your day.

(NB you may find need to keep that generated module, else the error will return. In that case, if you need to install a contrib module with the same name, remove the generated module after adding the contrib module. Then clear the cache.)

  • This was the simplest option after the SQL query above wouldn't work. – Chris Charlton Oct 19 '18 at 17:36

Now with the Configuration Management module the modules configuration is stored in the core.extension.yml file.

Go to edit the file and try to find the missing module from the filesystem then delete the line and import the config (drush cim).

If this not works but you has found the module, then create the module again (just the folder and a valid .info.yml file) and run again the drush cim command. This will uninstall the module.

  • 3
    This works, but the correct way is to restore the module and uninstall it. If that module provides schemas, configuration or so, it will remain in the system and you will have to clean it up manually otherwise. – Berdir Sep 13 '17 at 6:19
  • 1
    @Berdir if you can't find the custom module, we can do another thing? – Adrian Cid Almaguer Sep 13 '17 at 13:01
  • Not really, then you need to do it manually as suggested above with drush cedit or import/export in the core.extension file. – Berdir Sep 13 '17 at 13:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.