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,676 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,676 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 102.2K Reputation points

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

Cyber Sinh 6 Reputation points

2021-10-11T13:10:15.79+00:00

Same issue for me.
As workaround, I installed SQL Server 2019 in a linux container (docker) under WSL2.
It's still crazy that a major Microsoft software works better on Linux than on Windows.
Please sign in to rate this answer.

1 person found this answer helpful.
文通邓 6 Reputation points

2021-10-12T11:42:01.287+00:00

I did the same thing. But this method needs to be demonstrated when you are out on the Internet. The host cannot communicate with the Docker.

Cyber Sinh 6 Reputation points

2021-10-12T19:35:59.1+00:00

I can connect from SSMS under Windows to SQL Server 2019 under WSL2 with the IPv6 localhost address: ::1,1401
Sign in to comment
文通邓 6 Reputation points

2021-10-12T11:25:48.06+00:00

I also met the same problem and searched GOOGLE and BaiDu. Ran out of options!! First windows10, upgrade windows11 after the database service can not start, such as the official version out, installed the official version of windows11, the problem is still the same. Let's hope Microsoft supports SQL installation on windows11 soon.
Please sign in to rate this answer.

1 person found this answer helpful.
Robert Castles 31 Reputation points

2021-10-12T14:23:47.83+00:00

I tried the update the SQL server 2019 which was released about 7 days ago and it did not help either.
Sign in to comment

devon jerothe 6

Jumping on to mention I'm having the exact same issue.

Event viewer shows issues with ntdll.dll and sqllang.dll

This was on a fresh install on a formatted drive.

Faulting application name: sqlservr.exe, version: 2019.150.2000.5, time stamp: 0x5d8a9215
Faulting module name: ntdll.dll, version: 10.0.22000.120, time stamp: 0x50702a8c
Exception code: 0xc0000005
Fault offset: 0x00000000000357ae
Faulting process id: 0x1124
Faulting application start time: 0x01d7bf67449d262c
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8a318979-1413-46d7-8bbe-e0165f19cce8
Faulting package full name: 
Faulting package-relative application ID:

Tim Elliston 56 Reputation points

2021-10-15T10:08:51.263+00:00

I Have had exactly the same problem when I let my Samsung PRO 360 upgrade to Windows 11, my SQL Server instance service fails to start with an error 1067.

I called Microsoft about this following the official release and the wanted £400.00 fee to look into the issue, just because it was SQL Server, but clearly a windows 11 issue supporting SQL Server and SQL Server Express.

I concur that this is a hardware platform issue as the same setup works fine on my old SurfacePro4.

Just wish Microsoft would be more responsible and responsive about these issues instead of trying to charge huge fees to fix something they should be well aware of by now with the number of people with the issue which was reported many times through the Windows 11 pre-release phase too.
Please sign in to rate this answer.

1 person found this answer helpful.
Bernard Jurlina 21 Reputation points

2021-10-25T21:15:59.657+00:00

I had the problems with the sql sever 2019 on windows 11.
My solution was this. First, I have two disks in my laptop. One ssd with windows and the other is not ssd.
So, while installing the sql server I choose data directories on the second disk for the sql server default data folders....and now my sql server 2019 is working fine under windows 11.

Maybe this can help someone.
B.

David Cearini 21 Reputation points

2021-10-26T09:47:18.663+00:00

Great!!!

Installing SQL Server 2019 on the second disk have solved the problem for me too!!!
But It's indipendent from the Disk type !! I have an M2 disk as Windows boot disk and an SSD as second disk but now SQL Server is runnig!

Thanks!!

Luís Assunção 111 Reputation points

2021-10-26T10:10:16.667+00:00

I confirm that installing in a secondary disk, not mattering the disk type, it installed!!! ![143783-image.png][1] [1]: /api/attachments/143783-image.png?platform=QnA

Tim Elliston 56 Reputation points

2021-10-26T10:38:37.217+00:00

That is an interesting solution, I'd not thought of that approach, unfortunately my laptop and brand new Samsung Galaxy Pro 360 and only has 1 drive.

My SQL server is working fine under Windows 10 but fails to start the SQL service as soon as Windows 11 upgrade is done. I tried installing a new instance of SQL under Windows 11 but again that SQL Server instance didn't start, failing with error 1067.

Did you uninstall SQL prior to upgrading to Windows 11, then reinstall SQL Server using your separate drive approach after windows 11 upgrade. Was yours a clean window 11 deployment?

Thanks.

Tim Elliston 56 Reputation points

2021-10-26T10:40:27.573+00:00

Maybe I could install SQL Server on an SD card inserted into the SD slot of my laptop. I think performance would be very poor though, but it would prove the point on my system.

Luís Assunção 111 Reputation points

2021-10-26T10:43:28.627+00:00

At first I upgraded from Win10 with SQL Server and the SQL Server wouldn't run. Then, I uninstalled with RevoUninstaller and installed again in C disk. Got every time the same error. Today, after several weeks, I installed on D disk and voilà, its installed... What a shame Microsoft... :\

David Cearini 21 Reputation points

2021-10-26T10:44:45.667+00:00

You can reduce the Partition Size and create a new partition with a new drive letter!
I think this sholud solve the problem!

Luís Assunção 111 Reputation points

2021-10-26T10:44:50.407+00:00

Is it possible for you to use an external disk with USB3 or USBC connection? It would help.

Bernard Jurlina 21 Reputation points

2021-10-26T10:46:17.65+00:00

Hi TimElliston!

I had a fresh installation of windows 11 on a new disk...so the sql server installation was fresh also.

Regards!

Tim Elliston 56 Reputation points

2021-10-26T10:47:25.023+00:00

SO only the data needs to be on a separate disk when installing the server instance, the SQL Server application etc can remain on C:?

Luís Assunção 111 Reputation points

2021-10-26T10:48:48.78+00:00

No. Install everything on D disk. When you pick the items you want to install, chose D disk to install. Create a folder if you which like this: ![143750-image.png][1] [1]: /api/attachments/143750-image.png?platform=QnA

Bernard Jurlina 21 Reputation points

2021-10-26T10:49:35.143+00:00

Yes, it seems so.
I didn't try to put the data on the second partition of the same disk.

David Cearini 21 Reputation points

2021-10-26T10:50:23.45+00:00

When you choose to install the instance on a new disk SQL Server leave the shared component on Disk C and move only the instance files.
I think you need only a 2/3 GB.

Tim Elliston 56 Reputation points

2021-10-26T10:52:23.207+00:00

Perfect, thank you. I will try that and report back.

Warren Kinley 56 Reputation points

2021-12-03T21:06:30.083+00:00

Thank you for this advice, I too have installed on my secondary SSD drive and it has worked! It's only taken my half a day though to sort this out. I wished I'd not upgraded to Windows 11.
Sign in to comment

Share via

SQL Server 2019 - Windows 11

27 additional answers