The SQL server 2019 installation failed in Windows Server 2025.

Question

The SQL server 2019 installation failed in Windows Server 2025.

Siji, Merlin 0

From the logs, we understood that, installation fails because Microsoft Visual Studio Tools for Applications (VSTA) 2017 - a dependency of the Integration Services (SSIS) feature - crashes during installation on Windows Server 2025.

log details:
-> In 'C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\summary.txt' we could find the following log: Feature: Integration Services Status: Failed Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, and then try the setup process again. Component name: Microsoft Visual Studio Tools for Applications 2017 Component error code: 232 Component log file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20260420_115953\VSTA_Cpu32_1.log Error description: VS Shell installation has failed with exit code -2147024664.

The issue is solved if we redo the installation step. But since, redo is not recommended, we wanted an apt solution for this issue to be fixed.

-> In 'C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20260420_115953\VSTA_Cpu32_1.log' we could find the following log: [1E88:0C80][2026-04-20T12:01:42]e000: MUX: ERROR: TaskExceptionHolder_UnhandledException [1E88:0C80][2026-04-20T12:01:42]e000: MUX: Stack: at System.Threading.Tasks.TaskExceptionHolder.Finalize() [1E88:0C80][2026-04-20T12:01:42]e000: MUX: Exception: Info: InnerException: Info: [1E88:0C80][2026-04-20T12:01:42]e000: MUX: ERROR: The request was aborted: The request was canceled. [1E88:0C80][2026-04-20T12:01:42]e000: MUX: Stack: at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.WebRequestExtensions.<>c__DisplayClass3.<GetResponseAsync>b__5(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endMethod, TaskCompletionSource`1 tcs) [2360:0640][2026-04-20T12:01:42]i304: Verified existing payload: .vsix at path: C:\ProgramData\Package Cache.unverified.vsix. [2360:0640][2026-04-20T12:01:42]i305: Verified acquired payload: .vsix at path: C:\ProgramData\Package Cache.unverified.vsix, moving to: C:\ProgramData\Package Cache\594F3B71F90160F473DBB77001D3EE6EA4EAC343\packages\Microsoft.VisualStudio.Tools.Applications.vsix. [1E88:16B8][2026-04-20T12:01:42]i000: MUX: Source confirmed [1E88:0C80][2026-04-20T12:01:42]i000: MUX: Metrics: ShouldSendData=True [1E88:0C80][2026-04-20T12:01:42]i000: MUX: Permission to upload: Yes [1E88:0C80][2026-04-20T12:01:42]i000: MUX: Preparing to serialize data. [1E88:0C80][2026-04-20T12:01:42]i000: MUX: Data serialized. [1E88:0C80][2026-04-20T12:01:42]e000: MUX: WARNING: Object synchronization method was called from an unsynchronized block of code. [1E88:0C80][2026-04-20T12:01:42]e000: MUX: Stack: at System.Threading.Mutex.ReleaseMutex() at Microsoft.Devdiv.Bootstrapper.MutexHolder.ReleaseMutex() at Microsoft.Devdiv.Bootstrapper.UserFeedback.MetricsVariable.EndAndSend(Boolean sendNow, Boolean hasPermisisonToUpload, UInt32 appId, String& storeXml) at Microsoft.Devdiv.Bootstrapper.UserFeedback.Metrics.Uninitialize(Boolean rebootInTheMiddleRequest, String& storeXml) [1E88:0C80][2026-04-20T12:01:57]i000: MUX: Watson Bucketting Parameters [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P1 - vsta_setup [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P2 - 15.0.27520.03 [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P3 - 15.0.27520 [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P4 - Install [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P5 - [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P6 - Crash: System.AggregateException [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P7 - 4d52d975 [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P8 - 39f [1E88:0C80][2026-04-20T12:01:57]i000: MUX: P9 - dd

Please note the following:

The windows server 2025 that we are using is a Virtual machine with no internet. The SQL is installed offline using package.

And this kind of offline SQL server 2019 installation worked properly with no issues, on windows server 2019 (which is also a VM with no internet).

0 comments

1 answer

Your answer

Answer 1

Akhil Gajavelly 1,830 Microsoft External Staff Moderator

Hi @Siji, Merlin ,

Looking at your logs closely, this isn't really a compatibility issue between SQL Server 2019 and Windows Server 2025 they're officially supported together. The real culprit is much simpler.

Your VSTA 2017 bootstrapper is trying to make a network call during installation, and since your VM has no internet, that request times out and crashes the installer. That's the -2147024664 error. The reason redo works is that the first failed attempt already downloaded and cached the VSTA payload locally, so the second run skips that network call entirely.

The cleanest fix no redo needed.

Before running your SQL Server installer, manually pre-stage the VSTA package cache. After your first failed installation attempt, you'll find this file already on the machine:

C:\ProgramData\Package Cache\594F3B71F90160F473DBB77001D3EE6EA4EAC343\

packages\Microsoft.VisualStudio.Tools.Applications.vsix

Just make sure this path and file exist before your next fresh installation. If you're doing this on a brand new VM, copy that folder over from a previously failed install on another machine first, then run the installer it'll find the payload pre-cached and sail right through SSIS/VSTA without needing any network access.

No architecture changes, no SQL Server 2022 upgrade needed. Hope this saves you some time.

Thanks,
Akhil.

Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-04-28T05:59:23.7866667+00:00

Hi @

Just checking in were you able to try the VSTA pre-caching approach?

Since your environment is fully offline, this method usually avoids the VSTA bootstrapper failure by eliminating the network call altogether. If you’ve had a chance to test it, it would be helpful to know whether it worked in your setup or if you’re still hitting the same error.

If not, we can look at a couple of alternative offline-safe approaches as well.

Thanks,
Akhil.
Siji, Merlin 0 Reputation points

2026-04-28T06:05:59.6833333+00:00

Hi, I have not yet got a chance to test this approach. I shall check and provide the info.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-05-07T08:41:00.0233333+00:00

Hi @Siji, Merlin ,

Just following up on this. Whenever you get a chance to test the pre-caching approach, please do share the results. That will help confirm whether the issue is fully resolved in your offline setup.

In the meantime, if you run into any blockers while testing (especially around locating or copying the VSTA cache), feel free to share details and we can help further.

Thanks,
Akhil.
Siji, Merlin 0 Reputation points

2026-05-08T07:30:20.08+00:00
Hi, I tried the following approach as suggested:

After first failed installation attempt, copied this file from that machine: C:\ProgramData\Package Cache\594F3B71F90160F473DBB77001D3EE6EA4EAC343\ packages\Microsoft.VisualStudio.Tools.Applications.vsix

Then, copied it to the fresh server to the same path: "C:\ProgramData\Package Cache\594F3B71F90160F473DBB77001D3EE6EA4EAC343\ packages"

Then started the installation of our application, which then ran the installation of SQL server 2019

-> But this resulted in an early failure of installation of SQL server 2019, with a different error log.
Erland Sommarskog 135.3K Reputation points MVP Volunteer Moderator

2026-05-08T12:05:29.7966667+00:00

Can you share these error logs?
Siji, Merlin 0 Reputation points

2026-05-11T05:17:44.4766667+00:00

Right now, we’re trying a few other workarounds. If those don’t work, I’ll reproduce the issue again and share the error logs.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-05-27T06:48:57.7266667+00:00

Hi @Siji, Merlin ,

Thank you for the update and for sharing the current status.

Just following up since some time has passed were you able to make any progress with the alternative workarounds you mentioned? If the issue is still occurring, please feel free to reproduce it again and share the latest error logs/details when available. That would help the community investigate further and better understand the root cause.

Looking forward to your update.

Thanks,
Akhil.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-08T05:24:29.31+00:00

Hi @Siji, Merlin ,

Just checking back to see whether this issue has been resolved or if you are still encountering the same behavior.

If you had an opportunity to test further, it would be helpful to know whether the problem remains reproducible and whether any configuration changes, updates, or troubleshooting steps affected the outcome.

An update on the current status would help the community determine whether additional investigation is needed and may also assist others who encounter a similar issue in the future.

Thanks,
Akhil.