Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • An even easier workaround is to re-enable Windows-10/Server-2019-compatible behavior by setting the ForcedPhysicalSectorSizeInBytes registry key as mentioned in the link in your answer. I used this workaround successfully on a NUC with Windows Server 2022.
    – Heinzi
    Commented Apr 18, 2022 at 10:35
  • Thank you! Initially, the trace flag solution seemed not to work for me. I've checked the log and it turned out that the flag is properly passed to the service but it has problems accessing the database file. I had to delete the instance (sqllocaldb delete mssqllocaldb) and recreated it. After that, everything seems ok.
    – gius
    Commented Jul 24, 2022 at 11:26