SQL Server 2019 - Windows 11

Luís Assunção 111

Hi guys... So, I installed Windows 11 available to the Insiders program, but unfortunately, I'm having a problem that was already caused in other versions of SQL/Windows. I already tried all the solutions related to this issue but none worked. So, I'm going to leave the details: ![129499-image.png][1] [1]: /api/attachments/129499-image.png?platform=QnA Overall summary: Final result: Failed: see details below Exit code (Decimal): -2061893606 Start time: 2021-09-06 09:39:22 End time: 2021-09-06 09:43:17 Requested action: Install Setup completed with required actions for features. Troubleshooting information for those features: Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Machine Properties: Machine name: LEXUS Machine processor count: 16 OS version: Microsoft Windows 11 Pro (10.0.22000) OS service pack: OS region: United States OS language: English (United States) OS architecture: x64 Process architecture: 64 Bit OS clustered: No Product features discovered: Product Instance Instance ID Feature Language Edition Version Clustered Configured Package properties: Description: Microsoft SQL Server 2019 ProductName: SQL Server 2019 Type: RTM Version: 15 SPLevel: 0 Installation location: C:\SQL2019\Developer_ENU\x64\setup\ Installation edition: Developer Product Update Status: None discovered. User Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: false AGTSVCACCOUNT: NT AUTHORITY\SYSTEM AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Manual ASBACKUPDIR: Backup ASCOLLATION: Latin1_General_CI_AS ASCONFIGDIR: Config ASDATADIR: Data ASLOGDIR: Log ASPROVIDERMSOLAP: 1 ASSERVERMODE: TABULAR ASSVCACCOUNT: <empty> ASSVCPASSWORD: <empty> ASSVCSTARTUPTYPE: Automatic ASSYSADMINACCOUNTS: <empty> ASTELSVCACCT: <empty> ASTELSVCPASSWORD: <empty> ASTELSVCSTARTUPTYPE: 0 ASTEMPDIR: Temp BROWSERSVCSTARTUPTYPE: Disabled CLTCTLRNAME: <empty> CLTRESULTDIR: <empty> CLTSTARTUPTYPE: 0 CLTSVCACCOUNT: <empty> CLTSVCPASSWORD: <empty> CLTWORKINGDIR: <empty> COMMFABRICENCRYPTION: 0 COMMFABRICNETWORKLEVEL: 0 COMMFABRICPORT: 0 CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20210906_093909\ConfigurationFile.ini CTLRSTARTUPTYPE: 0 CTLRSVCACCOUNT: <empty> CTLRSVCPASSWORD: <empty> CTLRUSERS: <empty> ENABLERANU: false ENU: true EXTSVCACCOUNT: <empty> EXTSVCPASSWORD: <empty> FEATURES: SQLENGINE FILESTREAMLEVEL: 0 FILESTREAMSHARENAME: <empty> FTSVCACCOUNT: <empty> FTSVCPASSWORD: <empty> HELP: false IACCEPTPYTHONLICENSETERMS: false IACCEPTROPENLICENSETERMS: false IACKNOWLEDGEENTCALLIMITS: false INDICATEPROGRESS: false INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\ INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\ INSTALLSQLDATADIR: <empty> INSTANCEDIR: C:\Program Files\Microsoft SQL Server\ INSTANCEID: MSSQLSERVER INSTANCENAME: MSSQLSERVER ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service ISMASTERSVCPASSWORD: <empty> ISMASTERSVCPORT: 8391 ISMASTERSVCSSLCERTCN: <empty> ISMASTERSVCSTARTUPTYPE: Automatic ISMASTERSVCTHUMBPRINT: <empty> ISSVCACCOUNT: NT AUTHORITY\Network Service ISSVCPASSWORD: <empty> ISSVCSTARTUPTYPE: Automatic ISTELSVCACCT: <empty> ISTELSVCPASSWORD: <empty> ISTELSVCSTARTUPTYPE: 0 ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service ISWORKERSVCCERT: <empty> ISWORKERSVCMASTER: <empty> ISWORKERSVCPASSWORD: <empty> ISWORKERSVCSTARTUPTYPE: Automatic MATRIXCMBRICKCOMMPORT: 0 MATRIXCMSERVERNAME: <empty> MATRIXNAME: <empty> MRCACHEDIRECTORY: NPENABLED: 0 PBDMSSVCACCOUNT: <empty> PBDMSSVCPASSWORD: <empty> PBDMSSVCSTARTUPTYPE: 0 PBENGSVCACCOUNT: <empty> PBENGSVCPASSWORD: <empty> PBENGSVCSTARTUPTYPE: 0 PBPORTRANGE: <empty> PBSCALEOUT: false PID: ***** QUIET: false QUIETSIMPLE: false ROLE: RSINSTALLMODE: DefaultNativeMode RSSVCACCOUNT: <empty> RSSVCPASSWORD: <empty> RSSVCSTARTUPTYPE: Automatic SAPWD: ***** SECURITYMODE: SQL SQLBACKUPDIR: <empty> SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS SQLJAVADIR: <empty> SQLMAXDOP: 8 SQLMAXMEMORY: 2147483647 SQLMINMEMORY: 0 SQLSVCACCOUNT: NT AUTHORITY\SYSTEM SQLSVCINSTANTFILEINIT: false SQLSVCPASSWORD: ***** SQLSVCSTARTUPTYPE: Automatic SQLSYSADMINACCOUNTS: LEXUS\despo SQLTELSVCACCT: NT Service\SQLTELEMETRY SQLTELSVCPASSWORD: <empty> SQLTELSVCSTARTUPTYPE: Automatic SQLTEMPDBDIR: <empty> SQLTEMPDBFILECOUNT: 8 SQLTEMPDBFILEGROWTH: 64 SQLTEMPDBFILESIZE: 8 SQLTEMPDBLOGDIR: <empty> SQLTEMPDBLOGFILEGROWTH: 64 SQLTEMPDBLOGFILESIZE: 8 SQLUSERDBDIR: <empty> SQLUSERDBLOGDIR: <empty> SUPPRESSPAIDEDITIONNOTICE: false SUPPRESSPRIVACYSTATEMENTNOTICE: false TCPENABLED: 0 UIMODE: Normal UpdateEnabled: true UpdateSource: MU USEMICROSOFTUPDATE: false USESQLRECOMMENDEDMEMORYLIMITS: false X86: false Configuration file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20210906_093909\ConfigurationFile.ini Detailed results: Feature: Database Engine Services Status: Failed Reason for failure: An error occurred during the setup process of the feature. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A001A Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes. Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.4013.40&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026 Feature: SQL Browser Status: Passed Feature: SQL Writer Status: Passed Feature: SQL Client Connectivity SDK Status: Passed Feature: SQL Client Connectivity Status: Passed Rules with failures or warnings: Global rules: Warning IsFirewallEnabled The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at https://go.microsoft.com/fwlink/?linkid=2094702 for information about ports to open for each feature. Rules report file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20210906_093909\SystemConfigurationCheck_Report.htm

Robert Castles 31 Reputation points

2021-10-06T16:01:20.583+00:00

I have the same issue. I have tried everything I can think of. Will check the feedback hub
Luís Assunção 111 Reputation points

2021-10-06T20:24:33.73+00:00

If you find anything, let me know. I'm using a old laptop just to work with Microsoft Dynamics NAV since my computer is already using Windows 11 and don't want to go back to Windows 10... :\
ssboy 1 Reputation point

2022-04-20T13:45:37.21+00:00

which hdd type on your pc?

my hdd is samsung ssd 980 m.2,and i cannot install sqlserver 2019 too

someone told me that maybe the win11 has some problem with the m.2 hdd
Robert Castles 31 Reputation points

2022-04-20T17:28:18.37+00:00

Yes, it's looking very evident there is an issue with this particular hard drive. I have the same. I ended up installing SQL in docker linux for now. It works pretty well.

Accepted answer

Leon Laude 85,666 Reputation points

2021-09-06T10:28:07.433+00:00

Hi anonymous user,

SQL Server 2019 is not yet officially supported on Windows 11, because Windows 11 has not been officially released yet.
This however doesn't necessarily mean that it won't work, but it has not been tested/verified by Microsoft so any issue may occur.

SQL Server 2019: Hardware and software requirements - Operating system support
https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-ver15?view=sql-server-ver15#operating-system-support

----------

If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

Best regards,
Leon
Please sign in to rate this answer.

2 people found this answer helpful.
Luís Assunção 111 Reputation points

2021-09-06T13:13:53.477+00:00

So, right now I can't use it. I need to wait, at least, the release of Windows 11 to be able to install it properly?

Leon Laude 85,666 Reputation points

2021-09-06T15:39:13.657+00:00

That would probably be the best yes :-)

Reza-Ameri 16,836 Reputation points

2021-09-06T15:55:06.503+00:00

Please make sure report this issue using the Feedback Hub app too.

AAYUSH RAJ VERMA 1 Reputation point

2022-01-08T09:00:25.183+00:00

do mysql is now available for window 11??

Murray, Andy 0 Reputation points

2023-09-06T20:46:32.31+00:00

I'm having the same issue. It is 2023 now and Win 11 Pro is certainly released. Any new advice here?

Erland Sommarskog 101.4K Reputation points MVP

2023-09-06T20:50:36.9966667+00:00

Microsoft has published an article with workarounds for the issue.
Sign in to comment

27 additional answers

Anil Ekmekci 21 Reputation points

2021-10-08T16:35:33.523+00:00

Hi,
Now Windows 11 has released but i have the same issue with same error. I can't resolve it.
Please sign in to rate this answer.

4 people found this answer helpful.
Luís Assunção 111 Reputation points

2021-10-08T16:42:35.047+00:00

It's true... @Leon Laude , can you share anything new about this?

ssboy 1 Reputation point

2022-04-20T13:48:21.317+00:00

what's your hdd type? my hdd is m.2 and I have the same problem

Robert Castles 31 Reputation points

2022-04-20T17:24:55.92+00:00

Which model?

Erland Sommarskog 101.4K Reputation points MVP

2022-04-20T20:58:45.853+00:00

See this article for workarounds.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment
Tim Elliston 56 Reputation points

2021-11-08T13:02:34.537+00:00

Does any one from Microsoft read these posts?
Please sign in to rate this answer.

4 people found this answer helpful.
Alex 26 Reputation points

2021-11-08T18:14:44.27+00:00

it seems not

Jörg Debus 66 Reputation points

2022-02-05T18:57:48.29+00:00

MS engineers reading this? I don't think so. All these forums are effective firewalls against nasty problem reports.

Erland Sommarskog 101.4K Reputation points MVP

2022-02-05T19:03:41.157+00:00

This is a forum for peer-to-peer support. You can see Microsoft engineers post here occasionally, but there is no reason to expect them to monitor these forums on a regular basis.

For this particular issue, Microsoft has issued a troubleshooting document: https://learn.microsoft.com/sv-se/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size.

Jörg Debus 66 Reputation points

2022-02-08T10:50:34.04+00:00

Hi Erland,
thanx for the hint.

I have seen the MS Info with the fixes on this topic, but it does not address the real problem:

The article defines a scenario#3 where an already on W10 installed SQL Server survives an in place upgrade to W11 and generates error from the bad blocksize on W11. The fix will cure that. But this scenario is not real: MS W11 compatibility checking blocks an in place upgrade of W10 systems with Samsung SSDs to W11. Attached pls. find the diagnostic report from an in place installation check showing the blocking:

It seems that the SQL people are not aware of this serious defect which could well also exist on the W11 based Windows server versions. It will hit some ten thousand of installations installed on modern hardware.

So my problem is to get attention to this problem of a MS Engineer. Do you know any path to achieve this?

Regards
JD

172243-final-part-of-the-diagnostic-report.txt

Erland Sommarskog 101.4K Reputation points MVP

2022-02-08T22:10:36.67+00:00

So Windows 11 blocks upgrade on such drives, but gladly performs fresh installs? Kind of hilarious.

So my problem is to get attention to this problem of a MS Engineer. Do you know any path to achieve this?

You can report bugs on https://feedback.azure.com/d365community/, but there is no guarantee that anything happens soon.

If you have a blocking issue, you would need to open a support case.

As for the solutions in the document I have not tried any of them myself. For the time being, I'm staying away from Windows 11.

Jörg Debus 66 Reputation points

2022-02-27T09:57:30.24+00:00

Hi Erland,

I have checked the actual posts in the feedback.Azure.com/d365community/. It does not seem to address problems with installation of W11, I'm afraid. So the situation is really a kind of hilarious.

This is that kind of a bug, that MS cannot handle: bugs relating from internal lack of consistent handling of claims.

The reason for this problem is clear and well documented: W11 disk drivers handle default physical sector sizes different from W10: W11 drivers use the sector size reported from the device whereas W10 sets the physical sector size to a maximum of 4096 which is in line with the currently published specs. A short screening of SSD 3 major offerings show, that Samsung SSD 980 seems to be the only one with a default sector size of larger than 4096. SQL Server has a clean position: They support devices for database storage with 5120 or 4096 physical sector size. The W11-Migration crew implemented this by blocking a box with Samsung SSD 980 PRO and SQL Server installed from upgrading.

To solve this deadlock, a fix was published which changes the driver behavior to set this maximum 4096 as with W10. Very easy: 3 lines of code. But unfortunately the W11 migration crew seems not to be noticed of that fix. This fully explains the crazy situation.

So how to alert the W11 Migration crew?

Erland Sommarskog 101.4K Reputation points MVP

2022-02-27T11:14:47.443+00:00

So how to alert the W11 Migration crew?

As I said, that would be by opening a support case. At least that the standard response we have for SQL Server issues, and my expertise lies with SQL Server, so I cannot say much about Windows 11.
Sign in to comment
Jonathan Potts 36 Reputation points

2021-11-15T00:06:36.767+00:00
So I am having this same issue and I think I narrowed down the cause. I am using a Samsung 980 SSD which seems to have issues with Windows 11.

On Windows 11, with my Samsung 980 SSD, I am getting the following:

C:\Windows\system32>fsutil fsinfo sectorinfo c: LogicalBytesPerSector : 512 PhysicalBytesPerSectorForAtomicity : 16384 PhysicalBytesPerSectorForPerformance : 16384 FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096 Device Alignment : Aligned (0x000) Partition alignment on device : Aligned (0x000) No Seek Penalty Trim Supported Not DAX capable Not Thinly-Provisioned

When on Windows 10, PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance were 4096 which is what the correct value should be I believe.
Please sign in to rate this answer.

4 people found this answer helpful.
Robert Castles 31 Reputation points

2021-11-15T00:12:40.45+00:00

That is an impressive find. I also am running Samsung 980 m.2

Imagine @Microsoft was checking this out! I am going to link your post on the feedback hub.

Alex 26 Reputation points

2021-11-15T06:59:05.947+00:00

I am using SSD Samsung 980 NVMe M.2 1000 Gb, yes it can be the root cause

Jacek Wolczuk 6 Reputation points

2021-11-15T11:22:34.997+00:00

Why did you connected the parameters values with SQL issue? How is that connected?
And - why the values supposed to be wrong? They could be different on new Windows version I belive.

To be honest Im not sure what are these parameters , but as far as I know, they could be modified.

Jonathan Potts 36 Reputation points

2021-11-15T15:27:07.147+00:00

From what I can tell, programs that are I/O intensive (like SQL Server) usually are manually aligned to the sectors. Because Windows 11 is reporting to SQL Server that the sector size is 16K, SQL Server is trying to use that sector size even though it should be 4K which causes the sectors to not be aligned correctly and probably causing some form of I/O exception when SQL server tries to start up/install.
Sign in to comment
David Cearini 21 Reputation points

2021-10-12T20:25:31.093+00:00
Same issue here, but If it could help I have 2 different Notebook, only one have the issue with Sql Server 2019.
The installation on a Microsoft Surface with exactly the same software configuration perfectly run.

I have done various test:

Installed a fresh windows 11 copy

Installed SQL server on Window 10, doing an update to Windows 11 after the installation

Installed SQL Server as first software before the updates, and after all the windows updates

Nothing change! Every time it works on the microsoft Surface and crash on the other notebook, so there is something in the hardware configutation that generate this problem.

UPDATE: I have created a Virtual Machine on my phisical Windows 11 machine using the same Windows 11 ISO and the same SQL Server installer and everything run!
I think that this confirm the Hardware compatibility problem! I'm using SQL Server on my virtual machine at this moment
Please sign in to rate this answer.

2 people found this answer helpful.
Anil Ekmekci 21 Reputation points

2021-10-13T10:44:50.117+00:00

One of my friend upgraded from Windows 10 to Windows 11 and he didn't met with these problems. He has HP Elitebook 840 G6 and i have HP Elitebook 840 G8 (newer version). So i am also suspicious for hardware compatibility.
Sign in to comment