Windows 11 and MSSQL do not get along (Veeam Users take note)

[Sky-Knight]

Troubleshooting operating system disk sector size greater than 4 KB - SQL Server

This article troubleshoots SQL Server installation or startup failures related to some new storage devices and device drivers exposing a disk sector size greater than the supported 4-KB sector size.

docs.microsoft.com

Veeam Backup Agent requires MSSQL, as such all of this applies.

If you have a system with NVME storage, and it upgrades to Windows 11, MSSQL will FAIL TO START, which will also prevent your backup agent from working.

Workaround is to force the system to do what Windows 10 and previous versions did with this:

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name   "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"

I don't use Veeam, because its server side dependence on Microsoft turns my stomach. And now that I know that the desktop backup agent ALSO requires it... as far as I'm concerned it can negotiate a landing in the nearest dumpster! There's zero excuse for a heavy DB engine to be deployed on each endpoint just to back it up... We have VSS, use it darn it!

But I'm posting this here anyway because I know many are going to run into this. MSSQL on Windows 11 needs work... buckets of it.