Warnings should be reserved for universal issues affecting your site functionality and that are actionable. I wholeheartedly agree with this proposal. (See #2880374: Experimental modules and themes should not have warnings after being installed, #2877128: Evaluate status report warnings and determine which should be reduced to info, removed, etc., and #2766491: Update status should indicate whether installed contributed projects receive security coverage for more discussion)

But once a decision is made to disable it, the site shouldn't be reminding the user. Having update enabled by default with the shipped profiles is a good idea, and possibly throwing a warning when trying to disable it. IMHO it should not be used to pester people to do certain things. You use a custom update system, or a distribution performs updates for you.Your infrastructure doesn't allow the webs to reach the internet.Your site has a requirement to not report statistics/contact the cloud.

Some drupal hosting companies provide remote updates for customers, and customers should not be updating their sites on their own.There are 4 reasons (I can think of) why update module may need to be disabled: PHP 8.0 & MySQL 5.7 Patch Failed to Apply.

Download cyberduck 8.5.0