135 questions
You are running into a known issue where Windows 11 for some disk drives reports a sector size that SQL Server does not cope with. Microsoft has published an article with workarounds for the problem.
After upgrading to Windows 11, the Sql Server crashes.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 72%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
Jan Vávra
386
Reputation points
I had originally a Sql Server 2019 version. After upgrade, it didn't start. I uninstalled it and installed Sql Server version 2022. But this version is also unable to start.
I tried to run it in a single user mode without any success.
One weird thing is it still claims I am still running Windows 10,
ERRORLOG.txt
systeminfo returned
C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Binn>systeminfo
Host Name: VAVRA-PC
OS Name: Microsoft Windows 11 Enterprise
OS Version: 10.0.22631 N/A Build 22631
OS Manufacturer: Microsoft Corporation
{count} votes
-
Viorel 121.3K Reputation points2025-03-19T15:38:22.5633333+00:00 What details about the crash were observed?
Sign in to comment
Accepted answer
-
Erland Sommarskog 120.2K Reputation points MVP2025-03-19T22:47:02.51+00:00 -
Jan Vávra 386 Reputation points
2025-03-20T08:20:10.32+00:00 Thank you very much. I made these steps:
- fsutil fsinfo sectorinfo c:
originally returned
PhysicalBytesPerSectorForPerformance : 16384 - after adding a registry key
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device:and restarting Windows it newly shows:
PhysicalBytesPerSectorForPerformance : 4096
- The sql server then failed to start. But in the ERROR.log was nothing about process crash, there was:
2025-03-20 09:05:19.05 spid50s FCB::Open failed: Could not open file D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\model.mdf for file number 1. OS error: 3(Systém nemůže nalézt uvedenou cestu.).
- So I recreated master and other basic databases using
f:\>setup.exe /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS="vavra"Finally, the sql server has started ;-)
- fsutil fsinfo sectorinfo c:
-
Erland Sommarskog 120.2K Reputation points MVP
2025-03-20T21:40:32.23+00:00 Great to hear that you were able to work past the incorrect file path. (Which I believe comes from the template.) I'm not sure I would have figured that out myself.
Sign in to comment -
1 additional answer
Sort by: Most helpful
-
Jan Vávra 386 Reputation points
2025-03-19T16:55:37.27+00:00 I can see a STACK OVERFLOW exception in log from another run ...
2025-03-19 16:46:22.98 spid44s 03/19/25 16:46:22 Stack Overflow Dump not possible - Exception c00000fd EXCEPTION_STACK_OVERFLOW at 0x00007FFAD071F009-
Viorel 121.3K Reputation points
2025-03-19T17:10:03.44+00:00 Maybe this is a similar problem:
Sign in to comment -