This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
As I posted on StackOver flow here ... I'm unable use SQL 2019 Dev Edition after upgrading to Windows 11. I've tried uninstalling and installing but keep getting SQL Server Setup failed to restore the instance id. As you can see from my stackoverflow link, the SQL 2019 Dev Edition install reports a Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
I've tried manually removing per this article here. But still get the same error.
I've run sfc /scannow ... no errors reported
I've run DISM (DISM /online /cleanup-image /scanhealth, DISM /online /cleanup-image /checkhealth, DISM /online /cleanup-image /restorehealth
If I run SQL 2019 Dev Edition installer on my other Windows 10 PC, I have no issues at all.
So there seems to be some problem with the SQL 2019 Dev Edition installer on Windows 11 PC when there was a prior version of SQL installed on Windows 10 that was upgraded to Windows 11.
![](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(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
Hi @Rob Ainscough ,
The issue is related to system disk sector size greater than 4 KB:
This article provides solutions for troubleshooting errors during installation or starting SQL Server on Windows 11:
That is likely to be the reason why SQL Server stopped working. Alas, I'm afraid that the error that Rob runs into now is not related to this, but is due to other factors. Once he gets past those, it is not unlikely that he would face the disk-sector issue.
Hi @Yitzhak Khabinsky ,
The sector size for all the SSD/HDD drives on my PC are 512 Bytes/Sector so I don't think this is the problem.
I'm going to try this solution (change the SQL server account that it runs under) and report back if this works or fails.
I think I'm a victim of Microsoft accidentally make Windows 11 22H2 upgrade available to all per this article.
Cheers, Rob.
It might have been a mistake to uninstall. There is a known issue with Windows 11 and some SSDs and for which there is a simple workaround when you already have SQL Server installed.
Also, I like to point out that it is a foregone conclusion that this issue is related to the Win 11 upgrade. You machine may already have had a disorder, so if you had performed this uninstall + install while you still were on Windows 10, you would have faced the same issue.
I have seen people running into this error before, but I don't think I have ever understood what is going on. But the file to look at is Details.txt in the install folder. It is very verbose and far from always easy to make sense from.
OMG, 2 days later ... big thank you!!
This:
REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f
resolved the issue for my Windows 11 PC ... I'm eternally grateful, but at the same time I'm unbelievably pissed off at Microsoft for their incompetence ... 2 days of my life wasted on this.
Cheers, Rob.
Glad I bumped into this one. I was about to uninstall... After finding the msc I had no SQL Services!
Added the key and verified, then downloaded the Dev-edition iso, mounted, ran Repair, hit Escape for dozens of non-mapped login to securityID dialogs, and all "Successful".
Gratitude to all the above respondents for the info, refs, solutions, reassurance, and successful recovery from what ought not to have been an issue had MS done things right.