New instance of SQL Server 2017. I chose to install up to CU25 during the initial installation. Been using the database for a few months, but it seems to have a memory leak when using memory-optimized tables which causes it to crash overnight sometimes.

I have another instance with the same jobs and hardware on CU20 and it has never had this problem. Leads me to believe this is a CU25 issue.

I'd like to downgrade to CU20 to see if this fixes the issue. What is the best way of doing this?

  • Why not just spin up another (development) instance of 2017 CU20, and do a backup restore (or however you'd prefer to copy the data over) to it, to see if the problem replicates. Conversely, you can also spin up another CU25 instance as well and see if the problem is replicated.
    – J.D.
    Sep 11, 2021 at 12:34

1 Answer 1


The instructions for uninstalling CU25 can be found on the support page for that cumulative update:

How to uninstall this update on Windows

  1. In Control Panel, open the Programs and Features item, and then select View installed updates.
  2. Locate the entry that corresponds to this cumulative update package under SQL Server 2017.
  3. Press and hold (or right-click) the entry, and then select Uninstall.

For Linux, follow the instructions at Rollback SQL Server.

It is quite unusual to rollback a cumulative update. Be certain that is your best troubleshooting option before committing to it. You might want to do other troubleshooting or contact Microsoft Support about your issue on CU25 instead.

  • This worked. I hadn't been clicking on "view installed updates" so I thought there was no way to uninstall. Had forgotten that I'd installed the CU25 update a few days after the initial installation. Thanks!
    – eek
    Sep 12, 2021 at 17:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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