How to prevent auto-update of SQL Server 2025 Engine?

Jeff Foushee 96 Reputation points
2026-08-20T16:21:39.5566667+00:00

Hi. I am convinced of a JSON bug introduced somewhere between CU4 and CU6.

I want to reinstall my instances so I can troubleshoot and then post the bug if it exists.

I have repeatedly uninstalled my SQL Server 2025 instances.

I have reinstalled 3 RTM instances -- verified by at-at-version as 17.0.1000.7 --

and the next day it's back to version CU6-GDR, version 17.0.4060.2 .

I have disabled the CEIP service for each of the instances.

I have disabled Error and Usage Reporting for all instances.

EXECUTE sp_configure 'show advanced options'; EXECUTE sp_configure 'automatic updates' returns 'does not exist'.

What do I do to prevent my newly-installed RTM instance from automatically upgrading?

SQL Server Database Engine
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator
    2026-08-20T21:05:09.9766667+00:00

    There is no auto-update of Cumulative Updates by default. So if this happening, it is because it has been configured in your environment.

    GDRs for SQL Server comes with Windows Update, but if you only have the RTM version, you will be on the "RTM train", so you will get a GDR for RTM. But once you install a CU, the GDR update you will be offered will be CU6-GDR, as that is the most recent GDR, as I recall. I don't think there is a setting for Windows Update that will give you CUs. My guess is that you are in a corporate environment, and your IT folks have set something up.

    As for the configuration option "automatic updates", I think I recognise that from a blog post from Brent Ozar which he published on April 1st...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Deepesh Dhake 1,165 Reputation points
    2026-08-24T02:54:11.9433333+00:00

    SQL Server can't upgrade itself from RTM to a CU, there's no engine feature, service, or sp_configure option for it, which is why 'automatic updates' returns "does not exist." CEIP and error reporting are unrelated. Something external is applying the July 2026 CU6-GDR (17.0.4060.2).

    To find it: after the next overnight change, check the timestamped folder under ...\170\Setup Bootstrap\Log\ (Summary.txt + Detail.txt) for when the patch ran and what initiated it, and correlate with the Windows Update log.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.