Back to blog
Ronald Kraijesteijn, Founder
·November 19, 2026·7 min read

MDS broken after SQL Server 2022 CU27 or CU28: what to do while Microsoft works on a fix

Home/Blog/MDS broken after SQL Server 2022 CU27 or CU28: what to do while Microsoft works on a fix
Three updates, one MDS
CU26
KB5093420 · 16 Jul 2026 · 16.0.4265.3
The web app opens but shows no models, entities or data. The database is intact.
CU27
KB5104824 · 15 Sep 2026 · 16.0.4295.3
The data shows again. Creating an entity or an attribute fails, and Explorer may not load hierarchies.
CU28
KB5125472 · 12 Nov 2026 · 16.0.4325.4
The known issue is gone from the list. No MDS fix is listed, and admins report creating an entity still fails.

You install the latest cumulative update for SQL Server 2022, open Master Data Manager and create an entity. Save gives you a red exclamation mark and no message. On another server, Explorer stops loading hierarchies.

You are not alone, and your data is still there. Microsoft has listed this as a known issue since CU27 in September. Two months and one more update later, admins still report it. This post sets out what each update did, how to find the real error, and what you can do while Microsoft works on a fix.

What each update did to MDS

CU26: the web app went empty

CU26 (KB5093420) came out on 16 July 2026. After it, the MDS web app opened but showed no models, no entities and no data. The MDS database was intact. Admins on Microsoft Q&A found that uninstalling CU26 did not bring the screens back, because the files in Master Data Services\WebApplication\bin stayed at the new version.

CU27: the data came back, creating things broke

CU27 (KB5104824) followed on 15 September 2026. Several admins saw their data again. Microsoft added a known issue: creating an entity, creating an attribute and loading hierarchies in Explorer "might not load or work as expected". The KB says Microsoft is investigating a fix. It gives no workaround.

CU28: the known issue left the list, the problem did not

CU28 (KB5125472) came out on 12 November 2026. Its known issues no longer mention MDS, and its fix list does not mention MDS either. On 18 November an admin reported that creating an entity still fails after CU28. So treat the problem as open until a KB names the fix.

Check which update you run

Run this on the instance that holds the MDS database. A build of 16.0.4265.3 or higher means CU26 or later.

SELECT SERVERPROPERTY('ProductVersion')     AS Build,
       SERVERPROPERTY('ProductUpdateLevel') AS CU;

What to do today

  1. Find the real error. The exclamation mark hides it. Open the browser developer tools (F12), go to the Network tab and click Save again. One request fails and turns red. Its Response tab usually holds the actual message. Look in the Application log in Event Viewer on the MDS web server at the same time.
  2. Check the MDS database. Open Master Data Services Configuration Manager, select the MDS database and see if it offers an upgrade. The update replaces the web application files. The database upgrade is a separate step.
  3. Try the Excel add-in. The MDS Add-in for Excel can create an entity from a sheet, and a model administrator can add an attribute by publishing a new column. If that works on your server, you can keep going until a fix ships.
  4. Open a support case with Microsoft and refer to KB5104824. It is their own documented known issue, so you start from a known problem instead of a vague report.
  5. Back up before any rollback. Back up the MDS database and the WebApplication folder, and test the rollback on a copy first. After CU26, uninstalling the update did not restore the web files.

The patching problem this leaves you with

A cumulative update carries engine fixes, and some carry security fixes. If the MDS database shares an instance with your production databases, you now pick between a patched engine and a working MDS.

There are two ways out, and both cost time every month. You can move MDS to its own instance and patch it on a slower schedule. Or you can test every update on a copy of the MDS server before it reaches production. Write down which one you choose, because the next update will ask the same question.

Where MDS stands now

Microsoft removed MDS from SQL Server 2025. MDS in SQL Server 2022 follows that release: mainstream support until 11 January 2028 and extended support until 11 January 2033. So Microsoft still has to fix this, and it will get security fixes for years.

Still, the known issue has read "investigating a fix" since September, across two updates. That tells you how much attention MDS gets now. If your team planned to stay on MDS until 2028, this is a good week to check that plan.

If this is the moment you leave MDS

We build Primentra, a master data tool for teams on SQL Server, so take this part as our view. Three points matter for a team that sits on a broken MDS today.

  • MDS Direct Migration connects to the MDS database itself. It does not use the MDS web app, so a broken Master Data Manager does not stop it. It moves models, entities, attributes, members and explicit hierarchies, in under an hour for a typical model.
  • It rebuilds the subscription views of the leaf attributes as Integration Views, with the same names and the same columns. An ETL job that read the MDS view changes only its connection.
  • Primentra runs as its own Windows service with its own web app, on your own SQL Server. A SQL Server update patches the engine. It does not replace Primentra's files.

You can try it on a copy of your MDS model: the trial runs for 60 days on your own server. The migration page shows the five steps.

Common questions

Is my MDS data lost after SQL Server 2022 CU26 or CU27?

The reports so far say no. After CU26 the MDS web app showed no models or data, but the MDS database was intact. The failures sit in the web application. Back up the MDS database before you change anything.

Does SQL Server 2022 CU28 fix MDS?

Not as far as we can see. CU28 (KB5125472) no longer lists the MDS known issue, but its fix list does not mention MDS, and an admin reported on 18 November 2026 that creating an entity still fails after CU28.

Should I uninstall the cumulative update?

Only after a backup and a test on a copy. After CU26, admins found that uninstalling the update left the newer files in Master Data Services\WebApplication\bin, so the web app stayed broken. Back up the MDS database and that folder first.

Can I still migrate away from MDS while its web app is broken?

Yes, with a tool that reads the MDS database. Primentra MDS Direct Migration connects to the MDS database itself and does not use the MDS web app, so a broken Master Data Manager does not block it.

More from the blog

Your own SQL Server or your Fabric tenant: where should your master data live?6 min readThe port check is green and search is broken: monitoring an on-premises MDM server6 min readStaging Table Drift: How Primentra Catches a Column That Stopped Arriving9 min read

Ready to migrate from Microsoft MDS?

Download Primentra and run it on your own server, or try the live demo first. All features included.

Download free trialTry demoCompare MDM tools