In my case I decided to change the port used by Hyper-V Replica from 443 to 444. The result was that whenever SCVMM tried to use BITS to transfer a file – it would fail.įortunately – both BITS and Hyper-V Replica allow you to change the port that they use. SCVMM had also configured BITS to use certificate based authentication over port 443. If you have configured Hyper-V Replica to use certificate based authentication over port 443. Gracefully Shutdown the VM from inside the VM and then Retry the Process.Įither the VM that you have deployed is the Syspred VM. It is not a requirement for Windows applications to use the Windows Registry. Over time the computer suffers software rot as the registry fills with left-over and possibly incorrect entries. Winrm set winrm/config/Service stop winrmīelow also Could be the following reason’s.ĭo not turn off the VM from the Hyper-V or SCVMM Console. Click Start Scan to find Windows issues that could be causing PC problems. Initially start the troubleshooting from the WinRm run the below command on the Host. More details about the user.If you trying to Create A template and get’s the following error Message. 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 (MSIX). Since the developer's user.dat file was not registry keys, Windows throw that error message informing that the registry is corrupt. This error started to happen after the launching of MSIX, that now has the User.dat and Userclass.dat files to capture the registry keys. In this particular case, the user.dat file inside the package wasn't a Windows Registry file but a database file. In the root of the package that was causing the failure.

It was happening because the App package had a file called The Configuration registry database is corrupt The following error was happening for machines with the Windows 10 buildĪnd I could reproduce the issue in a machine with the version 1809.

This post is about an error that happened to an Desktop Bridge application that was published on Microsoft Store.

Configuration registry database corrupt