The module does not exist

By carlo_martini on 16 May 2019 at 10:49 UTC

I have this error in my Apache logs, when I try to install any (official) module.

[Thu May 16 12:20:01.283171 2019] [php7:notice] [pid 24843] Uncaught PHP Exception Drupal\\Core\\Extension\\Exception\\UnknownExtensionException: "The module hello does not exist." at /var/www/html/core/lib/Drupal/Core/Extension/ExtensionList.php line 522, referer: /admin/modules

That "hello" module in the error was a simple test that I made, following a guide, but it has been uninstalled and also removed from the filesystem. Also, the caches were emptied. So, why is it still looking for that?

Comments

Sounds like something went wrong with ...

mmjvb commented 15 January 2020 at 11:57

removing that module. Since it already was removed from the filesystem, suggest to remove it from the database as well.

Use SQL:delete from `key_value` where collection = 'system.schema' and name = 'hello';

That was it. Thanks!

carlo_martini commented 24 June 2019 at 10:58

That was it. Thanks!

Didn't work

bajah1701 commented 14 January 2020 at 20:24

I did that, updated database, cleared cache and I'm still getting the same error.

I find the cleanest way to

Jill L

she/her

commented 15 January 2020 at 05:14

I find the cleanest way to fix this issue is to re-download the module's code, and uninstall it (fixing the database issue), and THEN removing the code. This issue comes up when the module code is removed before it's properly uninstalled.

Worked for me.

keithn commented 17 January 2020 at 20:43

Thanks!

Actually the cleanest way would have been to ...

mmjvb commented 17 January 2020 at 23:27

retrieve that module from backup. In order for drupal to recognize it, it needs to be in the same location where is was when enabled. Also, it needs to be the same version as installed. Hopefully, it will uninstall properly.

Works! Thank you.

briangervais commented 22 April 2020 at 03:21

I executed `composer require drupal/missing-module` to re-download the module's core, then was able to uninstall it and fix my database issue.

See documentation for more complex scenario's

mmjvb commented 15 January 2020 at 11:06

https://www.drupal.org/node/2487215

worked for me.

yasheshb commented 8 April 2020 at 05:27

thank you @mmjvb

Yashesh Bhatia

works like a charm. thanks!

monph commented 11 May 2020 at 03:48

works like a charm. thanks!

It's worked fine.

manishdrupaldev commented 21 August 2023 at 09:44

Using below command, it helped me.

delete from `key_value` where collection = 'system.schema' and name = 'views_accordion';

Thanks!

thks manishdrupaldev

majidlahmidi commented 27 May 2024 at 13:15

it works

Awesome trick

nileshkhairnar commented 2 February 2024 at 11:38

That saves my day. Thanks!

Very handy

johnhanley commented 5 July 2024 at 01:22

I mistakenly renamed a custom module without uninstalling it first so this query fixed the aforementioned runtime error. Thank you.

@Jill, in my case it was a

bajah1701 commented 15 January 2020 at 13:47

@Jill, in my case it was a custom module which was already deleted from the file system and the computer as well as the recycle bin. Thankfully it worked after a few hours of ignoring it and doing something else. Don't why it took so long to realize that the module is no longer there.

Perhaps?

weynhamz

Ningbo

commented 17 March 2020 at 04:48

Perhaps?

drush cdel core.extension module.MODULE_NAME

Thanks, it works well!

Dmytro Litvinchuk commented 22 March 2020 at 20:49

It works, but after this, I had a problem to install the same module again...

This was the missing bit for me.

cbfannin commented 1 January 2021 at 17:06

I had a custom module that I renamed in the middle of development. I had already done everything else and this was the last piece that finally resolved the issue for me, thanks!

Thanks this solves my problem

samir_mankar commented 9 April 2021 at 06:37

Thanks this solves my problem.

Yes, this one worked for me

benjamin_dk commented 13 April 2021 at 19:16

Yes, this one worked for me too. Thanks.

Thanks!

charder commented 2 June 2021 at 16:43

Works perfectly!

Works for themes as well

Tyheman commented 21 September 2021 at 18:37

drush cdel core.extension theme.THEME_NAME

Worked

khurrami commented 22 March 2022 at 06:52

Thanks it worked

Thanks

digi_axlot commented 11 May 2022 at 20:44

It worked!

Still works! Removing swiftmailer!

treckstar commented 22 May 2024 at 19:59

Thanks, worked perfectly when trying to update a Drupal 9 site to Drupal 10, that had swiftmailer installed.

drush cim

In ExtensionList.php line 524:

The module swiftmailer does not exist.

drush cdel core.extension module.swiftmailer

drush cim

[success] The configuration was imported successfully.

it works

majidlahmidi commented 27 May 2024 at 13:16

thanks

Yes! Thank you sir!

garbo commented 13 January 2025 at 11:30

Yes! Thank you sir!

Thanks!

paulsally commented 22 April 2020 at 14:09

Deleting the record in key_value also solved my problem! Thanks!!

Awesome

chethan.thimmaiah commented 19 May 2020 at 11:01

This worked for me

$key_value = \Drupal::service

MykolaVeryha commented 27 May 2020 at 23:42

$key_value = \Drupal::service('keyvalue');
$key_value->get('system.schema')->delete('hello');

Delete module's system.schema key value works

dydave commented 4 September 2020 at 11:05

Thanks @Mykola Veryha for the code.

I can confirm it helped fixing the issue in my case:

After uninstalling the module properly from the back-end, I enabled devel and executed the code from devel/php.

The error then disappeared and I was able to run updates as expected.

Thanks again for the help!

Another solution ..

sumedha commented 1 March 2021 at 04:46

All the above solutions were perfect but my situation was a bit different. In my case none of the solutions were working, for the reason that it was a contributed module with errors. The error was due to unsupported version and some of my custom code . I was unable to figure out whats going wrong. It was not even getting uninstalled properly.

Then I deleted the module folder completely and run SQL command to delete "key_value" but not luck. I also tried composer install. Still there was an error for the missing module under status report.

Finally I created a new folder with same module name with a .info.yaml file and uninstalled the module form frontend. Guess what, my website is error free again :)

Thanks Sumedha

sanjayk commented 28 February 2021 at 21:57

Your solution work for me. I was also try to many thing but not luck.

Thanks

Thanks a lot

shyamkumawat commented 2 June 2021 at 05:03

This solution actully worked for me, tried multiple things but no result.

Getting same error for the module views_current_path

rajdattas commented 23 July 2021 at 19:29

I was getting the same error the module views_current_path does not exist at /Drupal/Core/Extension/ExtensionList.php line 522. This was happening while installing image captcha sub module from Captcha module. I was missing Views Current Path contributed module to install. After installing this module my error got resolved. You might also be missing some dependency module please check for it.

through config, drush, and editor

svetlio commented 14 April 2026 at 19:37

With drush export config: drush cex

edit core.extension.yml file, delete the row with the module_name, save

then import config: drush cim -y

The module does not exist

Comments

New forum topics