SQL Server 2022 error when downloading – taking more than 24 hours and still not resolved!

James Flush 0 Reputation points
2025-02-21T15:45:18.37+00:00

From my research, it seems that everyone is facing this issue, yet there is still no solution. I’m not sure what Microsoft is waiting for to fix this problem.

I have completely uninstalled and reinstalled it, but I keep encountering the same issue.

I have also changed the download location and tried different drivers, but the problem persists.

I have attempted to re-download it multiple times using different options, yet the issue remains!

This is the error log i am getting when trying to download it:

2025-02-21 06:55:02.28 Server Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64)

Oct 8 2022 05:58:25

Copyright (C) 2022 Microsoft Corporation

Standard Edition (64-bit) on Windows Server 2025 Standard Evaluation 10.0 (Build 26100: ) (Hypervisor)

2025-02-21 06:55:02.28 Server UTC adjustment: -8:00

2025-02-21 06:55:02.28 Server (c) Microsoft Corporation.

2025-02-21 06:55:02.28 Server All rights reserved.

2025-02-21 06:55:02.28 Server Server process ID is 11520.

2025-02-21 06:55:02.28 Server System Manufacturer: 'Supermicro', System Model: 'Super Server'.

2025-02-21 06:55:02.28 Server Authentication mode is MIXED.

2025-02-21 06:55:02.28 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\Log\ERRORLOG'.

2025-02-21 06:55:02.28 Server The service account is 'NT Service\MSSQL$MSSQLSERVER1'. This is an informational message; no user action is required.

2025-02-21 06:55:02.28 Server Registry startup parameters:

-d D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\DATA\master.mdf

-e D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\Log\ERRORLOG

-l D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\DATA\mastlog.ldf

2025-02-21 06:55:02.28 Server Command Line Startup Parameters:

-s "MSSQLSERVER1"

-m "SqlSetup"

-Q

-q "SQL_Latin1_General_CP1_CI_AS"

-T 4022

-T 4010

-T 3659

-T 3610

-T 8015

2025-02-21 06:55:02.28 Server SQL Server detected 1 sockets with 64 cores per socket and 128 logical processors per socket, 128 total logical processors; using 48 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2025-02-21 06:55:02.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2025-02-21 06:55:02.28 Server Detected 524134 MB of RAM. This is an informational message; no user action is required.

2025-02-21 06:55:02.28 Server Using conventional memory in the memory manager.

2025-02-21 06:55:02.29 Server Detected pause instruction latency: 74 cycles.

2025-02-21 06:55:02.29 Server Spin divider value used: 1

2025-02-21 06:55:02.29 Server Page exclusion bitmap is enabled.

2025-02-21 06:55:02.39 Server Top level memory blocks allocated=0x7000

2025-02-21 06:55:02.55 Server Buffer Pool: Allocating 134217728 bytes for 83861548 hashPages.

2025-02-21 06:55:03.46 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2025-02-21 06:55:03.46 Server Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores.

2025-02-21 06:55:03.48 Server Buffer pool extension is already disabled. No action is necessary.

2025-02-21 06:55:03.51 Server CPU vectorization level(s) detected: SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2

2025-02-21 06:55:03.53 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.

2025-02-21 06:55:03.56 Server Query Store settings initialized with enabled = 1,

2025-02-21 06:55:03.57 Server The maximum number of dedicated administrator connections for this instance is '1'

2025-02-21 06:55:03.57 Server This instance of SQL Server last reported using a process ID of 13040 at 2/21/2025 6:54:44 AM (local) 2/21/2025 2:54:44 PM (UTC). This is an informational message only; no user action is required.

2025-02-21 06:55:03.59 Server Node configuration: node 0: CPU mask: 0x0000000055555555:0 Active CPU mask: 0x0000000055555555:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-02-21 06:55:03.59 Server Node configuration: node 1: CPU mask: 0x5555555500000000:0 Active CPU mask: 0x0000555500000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-02-21 06:55:03.59 Server Node configuration: node 2: CPU mask: 0x00000000aaaaaaaa:0 Active CPU mask: 0x00000000aaaaaaaa:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-02-21 06:55:03.59 Server Node configuration: node 3: CPU mask: 0xaaaaaaaa00000000:0 Active CPU mask: 0x0000aaaa00000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-02-21 06:55:04.03 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2025-02-21 06:55:04.03 Server Lock partitioning is enabled. This is an informational message only. No user action is required.

2025-02-21 06:55:04.05 Server In-Memory OLTP initialized on highend machine.

2025-02-21 06:55:04.06 Server [INFO] Created Extended Events session 'hkenginexesession'

2025-02-21 06:55:04.06 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.

2025-02-21 06:55:04.07 Server Total Log Writer threads: 4, Node CPUs: 4, Nodes: 4, Log Writer threads per CPU: 1, Log Writer threads per Node: 2

2025-02-21 06:55:04.10 Server Database Mirroring Transport is disabled in the endpoint configuration.

2025-02-21 06:55:04.10 Server clwb is selected for pmem flush operation.

2025-02-21 06:55:04.11 spid44s Warning ******************

2025-02-21 06:55:04.11 spid44s SQL Server started in single-user mode. This an informational message only. No user action is required.

2025-02-21 06:55:04.11 spid44s Starting up database 'master'.

2025-02-21 06:55:04.11 spid44s Error: 17053, Severity: 16, State: 1.

2025-02-21 06:55:04.11 spid44s DoDevIoCtlOut() DeviceIoControl() : Operating system error 234(More data is available.) encountered.

2025-02-21 06:55:04.12 Server CLR version v4.0.30319 loaded.

2025-02-21 06:55:04.14 spid44s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\DATA\master.mdf.

2025-02-21 06:55:04.15 spid44s Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)

2025-02-21 06:55:04.15 spid44s Stack Signature for the dump is 0x0000000000000000

2025-02-21 06:55:04.15 spid44s CDmpClient::ExecuteAllCallbacks started.

2025-02-21 06:55:04.15 spid44s XE_DumpCallbacks is executing...

2025-02-21 06:55:04.17 spid44s DumpCallbackSOS is executing...

2025-02-21 06:55:04.17 spid44s DumpCallbackEE is executing...

2025-02-21 06:55:04.18 spid44s DumpCallbackSE is executing...

2025-02-21 06:55:04.18 spid44s DumpCallbackSEAM is executing...

2025-02-21 06:55:04.19 spid44s DumpCallbackSSB is executing...

2025-02-21 06:55:04.20 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2025-02-21 06:55:04.22 spid44s DumpCallbackQE is executing...

2025-02-21 06:55:04.22 spid44s DumpCallbackFullText is executing...

2025-02-21 06:55:04.22 spid44s DumpCallbackSQLCLR is executing...

2025-02-21 06:55:04.22 spid44s DumpCallbackHk is executing...

2025-02-21 06:55:04.24 spid44s DumpCallbackRepl is executing...

2025-02-21 06:55:04.24 spid44s DumpCallbackPolyBase is executing...

2025-02-21 06:55:04.24 spid44s CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.

2025-02-21 06:55:08.10 spid44s External dump process return code 0x20000001.

External dump process returned no errors.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,656 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dan Guzman 9,266 Reputation points
    2025-02-21T18:34:27.26+00:00

    Although you mention problem downloading, it seems the download was successful but a problem occurred during installation. This message from the error log you provided is especially of interest because it indicates a known issue with SQL Server and SSD disk sector size on Windows 11:

    2025-02-21 06:55:04.14 spid44s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER1\MSSQL\DATA\master.mdf.

    See this article for resolutions, which include installing on a different drive or adding a registry entry to change Windows 11 behavior.

    1 person found this answer helpful.
    0 comments No comments

  2. ZoeHui-MSFT 41,126 Reputation points
    2025-02-24T01:45:12.8366667+00:00

    Hi @James Flush,

    SQL Server detected 1 sockets with 64 cores per socket and 128 logical processors per socket, 128 total logical processors; using 48 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

    You are using Windows 11, there is a known issue when you install sql server 2022 on Windows 11.

    Try one of the resolutions in this article.

    Regards,

    Zoe Hui

    If the answer is helpful, please click "Accept Answer" and upvote it.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.