{"id":23814,"date":"2026-09-23T08:22:21","date_gmt":"2026-09-23T06:22:21","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&p=23814"},"modified":"2026-09-23T08:22:22","modified_gmt":"2026-09-23T06:22:22","password":"","slug":"disable-automatic-wordpress-updates","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/wordpress\/wordpress-automatische-updates-deaktivieren\/","title":{"rendered":"WordPress updates automatically \u2013 disable automatic core updates"},"content":{"rendered":"

You have disabled automatic WordPress updates in Softaculous \u2013 and yet WordPress suddenly updates itself to a new version?<\/p>\n\n\n\n

That is no contradiction. WordPress has a custom mechanism for automatic core updates<\/strong>, which can operate independently of Softaculous. Therefore, a WordPress installation can be updated automatically even though \u00abDo not auto-upgrade\u00bb is explicitly set in Softaculous.<\/p>\n\n\n\n

Especially with productive websites, WooCommerce shops, or installations with many plugins, an unplanned core update can be problematic. A new WordPress version can contain changes with which a theme, plugin, or used PHP version is not yet fully compatible.<\/p>\n\n\n\n

\n

Important:<\/strong> Automatic updates are fundamentally a security feature and not bad per se. If you completely disable them, you must ensure yourself that security and maintenance updates are checked and installed promptly.<\/p>\n<\/blockquote>\n\n\n\n

Why does WordPress even update automatically?<\/h2>\n\n\n\n

In a WordPress installation, several independent mechanisms can influence automatic updates.<\/p>\n\n\n\n

These include in particular:<\/p>\n\n\n\n

    \n
  • the settings of WordPress itself,<\/li>\n\n\n\n
  • an installer or management system like Softaculous,<\/li>\n\n\n\n
  • separate automatic updates for plugins,<\/li>\n\n\n\n
  • separate automatic updates for themes,<\/li>\n\n\n\n
  • Constants and filters within the WordPress configuration.<\/li>\n<\/ul>\n\n\n\n

    Therefore, it is not always enough to disable automatic updates in just a single place.<\/p>\n\n\n\n

    A typical case looks like this:<\/p>\n\n\n\n

    In Softaculous, the WordPress installation states:<\/p>\n\n\n\n

    Automatic WordPress core update:\nDo not update automatically<\/code><\/pre>\n\n\n\n
    Nevertheless, WordPress installs a new WordPress version automatically.<\/p>\n\n\n\n
    The reason could be that WordPress itself remains configured for automatic core updates<\/strong>.<\/p>\n\n\n\n
    What is the WordPress core?<\/h2>\n\n\n\n
    With the WordPress Core<\/strong> the actual WordPress software is meant. Plugins and themes are not part of the core and have their own update mechanisms.<\/p>\n\n\n\n
    For example, when WordPress itself is updated from one version to a newer version, it is a core update.<\/p>\n\n\n\n
    If, on the other hand, Elementor, WooCommerce, or another plugin is updated, it is a plugin update. The same applies accordingly to themes.<\/p>\n\n\n\n
    \n
    Important:<\/strong> Disabling automatic WordPress core updates does not automatically disable the updating of plugins or themes. These settings must be controlled separately.<\/p>\n<\/blockquote>\n\n\n\n
    Distinguish between major, maintenance, and security updates<\/h2>\n\n\n\n
    WordPress distinguishes between different types of updates when it comes to automatic core updates.<\/p>\n\n\n\n
    In simple terms, a distinction can be made between major version upgrades and maintenance and security updates.<\/p>\n\n\n\n
    Update Art<\/th>Meaning<\/th><\/tr><\/thead>
    Major update<\/strong><\/td>Major WordPress version with new features and potential technical changes<\/td><\/tr>
    Maintenance update<\/strong><\/td>Minor corrections and bug fixes within an existing version series<\/td><\/tr>
    Security update<\/strong><\/td>Fixes known or relevant security issues<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    This distinction is important for a productive website. A security update should normally be installed as soon as possible. In the case of a major version change, on the other hand, it may be advisable to check the compatibility of the plugins used, the theme, and the PHP version beforehand.<\/p>\n\n\n\n
    Check current status directly in WordPress<\/h2>\n\n\n\n
    WordPress displays in the administration area which automatic core updates are currently activated.<\/p>\n\n\n\n
    To do this, open:<\/p>\n\n\n\n
    WordPress Dashboard \u2192 Updates<\/code><\/pre>\n\n\n\n
    Below the current WordPress version you will find a note regarding the status of automatic updates.<\/p>\n\n\n\n
    Depending on the configuration, different messages may appear there.<\/p>\n\n\n\n
    Case 1: All new WordPress versions are installed automatically<\/h2>\n\n\n\n
    If WordPress displays a message along the lines of:<\/p>\n\n\n\n
    \n
    This website is automatically kept up to date by all new WordPress versions.<\/p>\n<\/blockquote>\n\n\n\n
    then automatic updates are also enabled for new major WordPress versions.<\/p>\n\n\n\n
    In this state, WordPress offers a link that allows you to switch to automatic updates for maintenance and security updates only.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    This is a possible explanation for why WordPress suddenly updated to a new version, even though, for example, Softaculous was set to \u00abDo not auto-upgrade.\u00bb.<\/p>\n\n\n\n
    Case 2: Automatically install only maintenance and security updates<\/h2>\n\n\n\n
    If you disable automatic major updates, WordPress can still automatically install maintenance and security updates.<\/p>\n\n\n\n
    WordPress then essentially shows:<\/p>\n\n\n\n
    \n
    This website is kept automatically up to date exclusively through maintenance and security updates for WordPress.<\/p>\n<\/blockquote>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    In this state, major new WordPress versions are no longer installed automatically. However, minor maintenance and security updates may still be applied automatically.<\/p>\n\n\n\n
    For many websites, this is a sensible compromise: major version upgrades are performed intentionally, while important minor fixes can still be installed automatically.<\/p>\n\n\n\n
    Case 3: Disable all automatic WordPress core updates<\/h2>\n\n\n\n
    If you also do not want to automatically install maintenance and security updates, you can completely disable the automatic updating of the WordPress core via the file wp-config.php<\/code> Deactivate.<\/p>\n\n\n\n
    The following constant is used for this:<\/p>\n\n\n\n
    define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
    After this change, WordPress shows in the area Dashboard \u2192 Updates<\/strong> according to:<\/p>\n\n\n\n
    \n
    This website does not receive automatic updates for new WordPress versions.<\/p>\n<\/blockquote>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    This clearly shows that WordPress itself should no longer automatically install new core versions.<\/p>\n\n\n\n
    Edit wp-config.php<\/h2>\n\n\n\n
    The file wp-config.php<\/code> is usually located in the root directory of your WordPress installation.<\/p>\n\n\n\n
    For a typical installation, this can be the following directory, for example:<\/p>\n\n\n\n
    public_html\/wp-config.php<\/code><\/pre>\n\n\n\n
    If WordPress was installed in a subdirectory, the file is located there accordingly.<\/p>\n\n\n\n
    Open the file using the file manager of your hosting account or via another suitable access to your website's files.<\/p>\n\n\n\n
    \n
    Attention:<\/strong> Create before changes to the wp-config.php<\/code> a backup of the file. A syntax error in this file can cause WordPress to stop loading correctly.<\/p>\n<\/blockquote>\n\n\n\n
    Completely disable automatic core updates<\/h2>\n\n\n\n
    Add the following line into the wp-config.php<\/code> a<\/p>\n\n\n\n
    define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
    The constant should be inserted before the final WordPress line, which, depending on the language of the installation, translates roughly to:<\/p>\n\n\n\n
    \/* That's all, stop editing! Happy publishing. *\/<\/code><\/pre>\n\n\n\n
    An excerpt can look like this, for example:<\/p>\n\n\n\n
    define( 'WP_AUTO_UPDATE_CORE', false );\n\n\/* That's all, stop editing! Happy publishing. *\/<\/code><\/pre>\n\n\n\n
    Then save the file.<\/p>\n\n\n\n
    Check if the setting has been applied<\/h2>\n\n\n\n
    Do not rely solely on the line in the wp-config.php<\/code> is available.<\/p>\n\n\n\n
    Open again afterwards:<\/p>\n\n\n\n
    WordPress Dashboard \u2192 Updates<\/code><\/pre>\n\n\n\n
    If the setting has been applied correctly, WordPress should indicate that the site will not receive automatic updates for new WordPress versions.<\/p>\n\n\n\n
    With that you can immediately check whether WP_AUTO_UPDATE_CORE<\/code> is taken into account by WordPress.<\/p>\n\n\n\n
    \n
    Control:<\/strong> When WordPress, after entering define( 'WP_AUTO_UPDATE_CORE', false );<\/code> continues to announce automatic core updates, it should be checked whether the constant is spelled correctly and in a suitable place in the wp-config.php<\/code> was inserted.<\/p>\n<\/blockquote>\n\n\n\n
    What values can WP_AUTO_UPDATE_CORE have?<\/h2>\n\n\n\n
    The constant WP_AUTO_UPDATE_CORE<\/code> can be set differently.<\/p>\n\n\n\n
    Configuration<\/th>Effect<\/th><\/tr><\/thead>
    define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/td>Disable automatic WordPress core updates<\/td><\/tr>
    define( 'WP_AUTO_UPDATE_CORE', true );<\/code><\/td>Enable automatic core updates comprehensively<\/td><\/tr>
    define( 'WP_AUTO_UPDATE_CORE', 'minor' );<\/code><\/td>Restrict automatic updates to minor core versions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    If you want to perform major version upgrades consciously yourself, but still want to continue receiving maintenance and security updates automatically, you can 'minor'<\/code> be a possible configuration.<\/p>\n\n\n\n
    If no WordPress core version at all should be installed without prior inspection, you use:<\/p>\n\n\n\n
    define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
    Why can Softaculous still display \u00abDo not auto-upgrade\u00bb?<\/h2>\n\n\n\n
    Softaculous and WordPress are two different systems.<\/p>\n\n\n\n
    Softaculous can install, manage, back up, and, depending on the configuration, also update WordPress. However, WordPress itself also has its own background updater.<\/p>\n\n\n\n
    If you disable automatic WordPress core updates in Softaculous, it initially means that Softaculous itself should not perform this automatic upgrade<\/strong>.<\/p>\n\n\n\n
    That doesn't necessarily disable the internal update mechanism of WordPress.<\/p>\n\n\n\n
    Exactly for this reason, the following situation can arise:<\/p>\n\n\n\n
    Softaculous:\nAutomatic update of WordPress core \u2192 Disabled\n\nWordPress:\nAutomatic update of all new WordPress versions \u2192 Enabled<\/code><\/pre>\n\n\n\n
    In this case, WordPress can still update itself.<\/p>\n\n\n\n
    \n
    Important:<\/strong> If you want to reliably control automatic updates, you should not only check your installer's setting, but additionally check the update status directly under WordPress Dashboard \u2192 Updates<\/strong> check.<\/p>\n<\/blockquote>\n\n\n\n
    Check Softaculous additionally<\/h2>\n\n\n\n
    If your WordPress installation is managed with Softaculous, you should also check there to see if automatic updates are enabled.<\/p>\n\n\n\n
    Open the relevant installation in the Softaculous WordPress Manager.<\/p>\n\n\n\n
    If automatic updates via Softaculous are not desired, the following option in the WordPress core settings should be selected accordingly:<\/p>\n\n\n\n
    Automatic WordPress core update:\nDo not update automatically<\/code><\/pre>\n\n\n\n
    On this occasion, also check the settings for plugins and themes.<\/p>\n\n\n\n
    Depending on the Softaculous configuration, automatic updates for:<\/p>\n\n\n\n
      \n
    • the WordPress core,<\/li>\n\n\n\n
    • WordPress plugins and<\/li>\n\n\n\n
    • WordPress themes<\/li>\n<\/ul>\n\n\n\n
      can be activated or deactivated separately.<\/p>\n\n\n\n
      Honor global Softaculous settings<\/h2>\n\n\n\n
      If you manage multiple WordPress installations, additional global Softaculous settings may be relevant.<\/p>\n\n\n\n
      Softaculous includes, among other things, specifications for automatic script updates and for the default settings of new installations.<\/p>\n\n\n\n
      A global setting can determine, for example, whether automatic upgrades are preselected for new installations.<\/p>\n\n\n\n
      Therefore, during troubleshooting you should both:<\/p>\n\n\n\n
        \n
      • as well as the global Softaculous configuration<\/li>\n\n\n\n
      • the settings of the specific WordPress installation<\/li>\n<\/ul>\n\n\n\n
        check.<\/p>\n\n\n\n
        However, one thing remains crucial: even if Softaculous is not supposed to perform updates, the internal WordPress updater can still be active independently of it.<\/p>\n\n\n\n
        What about automatic plugin updates?<\/h2>\n\n\n\n
        The constant:<\/p>\n\n\n\n
        define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
        regarding the WordPress Core<\/strong>.<\/p>\n\n\n\n
        It is not intended to control automatic updates of individual plugins.<\/p>\n\n\n\n
        WordPress can manage its own automatic updates for plugins. You can usually find the status under:<\/p>\n\n\n\n
        WordPress Dashboard \u2192 Plugins<\/code><\/pre>\n\n\n\n
        There, automatic updates can be enabled or disabled for individual plugins.<\/p>\n\n\n\n
        In addition, plugins, management tools, or hosting systems can use their own update mechanisms.<\/p>\n\n\n\n
        What about automatic theme updates?<\/h2>\n\n\n\n
        Themes are also managed independently of the WordPress core.<\/p>\n\n\n\n
        The attitude WP_AUTO_UPDATE_CORE<\/code> therefore does not automatically deactivate theme updates.<\/p>\n\n\n\n
        If you want to have complete control over updates, you should also check whether automatic updates are enabled for your installed themes.<\/p>\n\n\n\n
        Should automatic WordPress updates be completely disabled?<\/h2>\n\n\n\n
        There is no one-size-fits-all answer to that.<\/p>\n\n\n\n
        Automatic security and maintenance updates have one important advantage: security patches can be installed promptly without an administrator having to intervene manually first.<\/p>\n\n\n\n
        On the other hand, a productive website can consist of many interdependent components:<\/p>\n\n\n\n
          \n
        • WordPress Core,<\/li>\n\n\n\n
        • Theme,<\/li>\n\n\n\n
        • Plugins,<\/li>\n\n\n\n
        • PHP version,<\/li>\n\n\n\n
        • Database,<\/li>\n\n\n\n
        • Cache systems,<\/li>\n\n\n\n
        • WooCommerce and extensions,<\/li>\n\n\n\n
        • Interfaces to external services.<\/li>\n<\/ul>\n\n\n\n
          An update of a single component can therefore theoretically have an impact on other parts of the website.<\/p>\n\n\n\n
          Especially in the case of a WooCommerce store, a mission-critical website, or an installation with special plugins, it can make sense to carry out updates consciously and in a controlled manner.<\/p>\n\n\n\n
          \n
          Attention:<\/strong> Disabling automatic updates only makes sense if the website is actively maintained afterwards. A permanently outdated WordPress version poses a significantly greater risk than a controlled update.<\/p>\n<\/blockquote>\n\n\n\n
          Controlled updates instead of avoiding updates<\/h2>\n\n\n\n
          The goal should not be to avoid updating WordPress for as long as possible.<\/p>\n\n\n\n
          The goal is rather to be able to determine the timing of the update yourself and to control the impact.<\/p>\n\n\n\n
          Before a major WordPress update, it is particularly recommended to:<\/p>\n\n\n\n
            \n
          • ensuring a current backup,<\/li>\n\n\n\n
          • checking the compatibility of important plugins,<\/li>\n\n\n\n
          • to take the used theme into account,<\/li>\n\n\n\n
          • to check the PHP version and system requirements,<\/li>\n\n\n\n
          • to use a staging environment first for mission-critical websites if necessary.<\/li>\n<\/ul>\n\n\n\n
            After the update, core functions of the website should be tested.<\/p>\n\n\n\n
            In a WooCommerce shop, this includes, for example, the shopping cart, checkout, payment methods, email notifications, and important interfaces.<\/p>\n\n\n\n
            WordPress continues to update despite WP_AUTO_UPDATE_CORE<\/h2>\n\n\n\n
            If WordPress, despite:<\/p>\n\n\n\n
            define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
            continues to be updated automatically, the cause should be investigated in more detail.<\/p>\n\n\n\n
            Possible causes include, for example:<\/p>\n\n\n\n
              \n
            • an external WordPress management system,<\/li>\n\n\n\n
            • a hosting or installer system that forces updates,<\/li>\n\n\n\n
            • a plugin with its own update control,<\/li>\n\n\n\n
            • additional code in a plugin or theme,<\/li>\n\n\n\n
            • a second definition or an incorrect position of the constant,<\/li>\n\n\n\n
            • server-side management or maintenance functions.<\/li>\n<\/ul>\n\n\n\n
              In this case, it should first be checked whether, which system actually triggered the update<\/strong>, instead of disabling further update functions on suspicion.<\/p>\n\n\n\n
              The three update states at a glance<\/h2>\n\n\n\n
              WordPress ad<\/th>Meaning<\/th><\/tr><\/thead>
              All new WordPress versions are installed automatically<\/td>Even major new WordPress versions can be installed automatically.<\/td><\/tr>
              Only maintenance and security updates<\/td>Major version upgrades do not happen automatically, but smaller maintenance and security updates still do.<\/td><\/tr>
              No automatic updates for new WordPress versions<\/td>Automatic WordPress core updates are disabled<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
              Summary<\/h2>\n\n\n\n
              When WordPress updates automatically, even though automatic updates are disabled in Softaculous, it does not necessarily mean there is an error.<\/p>\n\n\n\n
              WordPress has its own mechanism for automatic core updates. This can be enabled independently of Softaculous.<\/p>\n\n\n\n
              You can check the current status under Dashboard \u2192 Updates<\/strong> check.<\/p>\n\n\n\n
              If only major automatic version upgrades should be prevented, you can restrict WordPress to automatic maintenance and security updates.<\/p>\n\n\n\n
              If WordPress should not automatically install any core version at all, you can do this in the wp-config.php<\/code> clearly define<\/p>\n\n\n\n
              define( 'WP_AUTO_UPDATE_CORE', false );<\/code><\/pre>\n\n\n\n
              After that, WordPress should be installed under Dashboard \u2192 Updates<\/strong> Confirm that no automatic updates for new WordPress versions are performed.<\/p>\n\n\n\n
              Plugin and theme updates are independent of this and must be checked separately.<\/p>\n\n\n\n
              Anyone who completely disables automatic core updates should not simply leave WordPress at an old version. Updates should instead promptly, consciously, and after a brief compatibility check<\/strong> to be carried out.<\/p>","protected":false},"excerpt":{"rendered":"
              Du hast automatische WordPress-Updates in Softaculous deaktiviert \u2013 und trotzdem aktualisiert sich WordPress pl\u00f6tzlich selbst auf eine neue Version? Das ist kein Widerspruch. WordPress besitzt einen eigenen Mechanismus f\u00fcr automatische Core-Updates, der unabh\u00e4ngig von Softaculous arbeiten kann. Deshalb kann eine WordPress-Installation automatisch aktualisiert werden, obwohl in Softaculous ausdr\u00fccklich \u00abNicht automatisch aktualisieren\u00bb eingestellt ist. Gerade bei […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[80],"doc_tag":[],"class_list":["post-23814","docs","type-docs","status-publish","hentry","doc_category-wordpress"],"year_month":"2026-09","word_count":2022,"total_views":"16","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"WordPress","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/wordpress\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/23814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=23814"}],"version-history":[{"count":2,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/23814\/revisions"}],"predecessor-version":[{"id":23820,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/23814\/revisions\/23820"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=23814"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=23814"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=23814"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}