The issue happened to an Desktop Bridge application that was published on Microsoft Store.
The developer started to receive some reports of the following error:
The Configuration registry database is corrupt
This error was happening for machines with the Windows 10 build higher than 17763.55 and I could reproduce the issue in a machine with the version 1809.
The error happened because the App package had a file called user.dat in the root of the package. This file was causing the failure.
That user.dat file is a binary file used by the App, but Microsoft app platform also looks for user.dat in the root of all packages in an attempt to interpret it as a registry file with registry keys. Since their user.dat file was not registry keys, Windows throw that error message informing that the registry is corrupt.
The reason the package works on the 1803 build of Windows is that Windows didn’t look for the existence of that user.dat file in 1803 – that check is a new feature, or ‘behavior’, in the case of the app.
I hope that it helps.