Setup issue to SQL Server Management studio installer 22

Question

Setup issue to SQL Server Management studio installer 22

Jonathan 85

Hi,

When doing the setup of SQL Server Management studio installer 22 on Windows server 2025, I got "internet connection, and not able to do the download". How to find out the issues on the server for this?

Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-05-31T09:42:33.8333333+00:00

What sort of machine does this happen on? Your private laptop at home? A server inside a company firewall?

I assume that the error message said "no internet connection", which speaks for itself. What troubleshooting have you conducted to check the internet connection?
Jonathan 85 Reputation points

2026-06-01T02:20:37.08+00:00

The issue is on the server 2025 having a designated public IP.
Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-06-01T21:10:18.6566667+00:00

So it is a server-operating system. That suggests that this is a corporate network. Which means that corporate policies could get in your way. Have you spoken to your IT folks?
Jonathan 85 Reputation points

2026-06-02T09:51:41.08+00:00

Only I am with this server. Any way to ensure the setup can be done?

Answer accepted by question author

Deepesh Dhake 80

It looks like problem is DNS, not connectivity or firewall. You can try following in order.

See what DNS actually does with the name:

Resolve-DnsName aka.ms
nslookup aka.ms

Check which DNS servers the box is using:

Get-DnsClientServerAddress
ipconfig /all

Look at the configured DNS server entries. If they're empty, pointing at a dead internal resolver, or pointing at something that only serves internal zones, that's your failure.

Test against a known-good public resolver to isolate the fault:

Resolve-DnsName aka.ms -Server 8.8.8.8
nslookup aka.ms 8.8.8.8

If 8.8.8.8 resolves it fine but your configured DNS doesn't, the problem is your DNS server / network config, not the host or the internet.

Check the hosts file for stray entries (this explains the earlier bogus-IP behavior):

C:\Windows\System32\drivers\etc\hosts

Flush and retry:

ipconfig /flushdns
Resolve-DnsName aka.ms

Jonathan 85 Reputation points

2026-06-03T02:52:11.45+00:00

FYI
Deepesh Dhake 80 Reputation points

2026-06-03T14:06:26.1333333+00:00

Looking at the output, IPv4 DNS server list on the network adapter is empty. The only DNS servers configured are IPv6 link-local addresses, and resolution through them times out. When you query 8.8.8.8 directly, it resolves instantly, so the network path works and DNS itself is reachable. The adapter just doesn't have a working DNS server assigned for normal resolution. That's why every Microsoft hostname fails and the SSMS installer reports "no internet connection."

You can try following fix:

Step 1:

Assign a working DNS server to the adapter (InterfaceIndex 9)
Set-DnsClientServerAddress -InterfaceIndex 9 -ServerAddresses ("8.8.8.8","1.1.1.1")

If there is any security policy to not to use public ipaddress then you can use:

Set-DnsClientServerAddress -InterfaceIndex 9 -ServerAddresses ("<internal dns ipaddress 1>","<internal dns ipaddress 2>")

Step 2:

ipconfig /flushdns

Step 3:

Resolve-DnsName aka.ms

Step 4:

If aka.ms resolves, re-test an installer host:

Test-NetConnection download.visualstudio.microsoft.com -Port 443
Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-06-03T18:58:25.3333333+00:00

In addition to Deepesh's post: I see Red Had VirtIO Ethernet Adapter. Am I right to assume that this is a virtual machine running on a Linux host? Not that this should matter as such, but there could be problems with the network configuration in the virtualisation software. I seem to recall that I have had similar problems.

Also, it is worth trying with a completely different target address, for instance, www.aftonbladet.se (that's a Swedish newspaper). I would expect that to produce the same error message, because it would be funny, it the DNS only failed for Microsoft addresses.
Jonathan 85 Reputation points

2026-06-04T04:34:44.93+00:00

Thanks a lot to all help.

Deepesh,

Could you help on it below if possible?

https://learn.microsoft.com/en-us/answers/questions/5906831/issue-to-access-ftp

2 additional answers

Your answer

Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-05-31T09:42:33.8333333+00:00

What sort of machine does this happen on? Your private laptop at home? A server inside a company firewall?

I assume that the error message said "no internet connection", which speaks for itself. What troubleshooting have you conducted to check the internet connection?
Jonathan 85 Reputation points

2026-06-01T02:20:37.08+00:00

The issue is on the server 2025 having a designated public IP.
Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-06-01T21:10:18.6566667+00:00

So it is a server-operating system. That suggests that this is a corporate network. Which means that corporate policies could get in your way. Have you spoken to your IT folks?
Jonathan 85 Reputation points

2026-06-02T09:51:41.08+00:00

Only I am with this server. Any way to ensure the setup can be done?
Jonathan 85 Reputation points

2026-06-03T02:52:11.45+00:00

FYI
Deepesh Dhake 80 Reputation points

2026-06-03T14:06:26.1333333+00:00

Looking at the output, IPv4 DNS server list on the network adapter is empty. The only DNS servers configured are IPv6 link-local addresses, and resolution through them times out. When you query 8.8.8.8 directly, it resolves instantly, so the network path works and DNS itself is reachable. The adapter just doesn't have a working DNS server assigned for normal resolution. That's why every Microsoft hostname fails and the SSMS installer reports "no internet connection."

You can try following fix:

Step 1:

Assign a working DNS server to the adapter (InterfaceIndex 9)
Set-DnsClientServerAddress -InterfaceIndex 9 -ServerAddresses ("8.8.8.8","1.1.1.1")

If there is any security policy to not to use public ipaddress then you can use:

Set-DnsClientServerAddress -InterfaceIndex 9 -ServerAddresses ("<internal dns ipaddress 1>","<internal dns ipaddress 2>")

Step 2:

ipconfig /flushdns

Step 3:

Resolve-DnsName aka.ms

Step 4:

If aka.ms resolves, re-test an installer host:

Test-NetConnection download.visualstudio.microsoft.com -Port 443
Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-06-03T18:58:25.3333333+00:00

In addition to Deepesh's post: I see Red Had VirtIO Ethernet Adapter. Am I right to assume that this is a virtual machine running on a Linux host? Not that this should matter as such, but there could be problems with the network configuration in the virtualisation software. I seem to recall that I have had similar problems.

Also, it is worth trying with a completely different target address, for instance, www.aftonbladet.se (that's a Swedish newspaper). I would expect that to produce the same error message, because it would be funny, it the DNS only failed for Microsoft addresses.
Jonathan 85 Reputation points

2026-06-04T04:34:44.93+00:00

Thanks a lot to all help.

Deepesh,

Could you help on it below if possible?

https://learn.microsoft.com/en-us/answers/questions/5906831/issue-to-access-ftp

Answer 1

Deepesh Dhake 80

You can try following check:

Test basic connectivity like "ping" test
Check proxy settings like "netsh winhttp show proxy".
Test HTTPS outbound like "Test-NetConnection -ComputerName aka.ms -Port 443"

Most likely causes:

Outbound port 443 blocked by firewall
Proxy required but not configured
Group Policy restricting internet access

Jonathan 85 Reputation points

2026-06-02T09:57:27.1133333+00:00

FYI
Deepesh Dhake 80 Reputation points

2026-06-02T15:18:29.83+00:00
Can you try without -computername? You are giving your computername with "-" so powershell taking it as parameter.

Test-NetConnection aka.ms -Port 443

You can check if TCP test is succeeded.

If TcpTestSucceeded is True, the network path is fine.

The actual payloads come from hosts like download.visualstudio.microsoft.com, dl.delivery.mp.microsoft.com, and Azure/Akamai CDNs. aka.ms:443 can succeed while a download host is blocked. Test those specifically:

Test-NetConnection download.visualstudio.microsoft.com -Port 443 Test-NetConnection dl.delivery.mp.microsoft.com -Port 443
Jonathan 85 Reputation points

2026-06-02T15:24:46.1033333+00:00

FYI
Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator

2026-06-02T19:10:49.3566667+00:00
Deepesh posted two commands, but unfortunately the line break disappeared somewhere. This is a corrected version:

Test-NetConnection download.visualstudio.microsoft.com -Port 443 Test-NetConnection dl.delivery.mp.microsoft.com -Port 443
Jonathan 85 Reputation points

2026-06-03T03:43:02.31+00:00

FYI

Answer 2

Use the Visual Studio Installer and SSMS logs to pinpoint why the SSMS 22 bootstrapper cannot download packages, and then validate network/offline prerequisites.

Confirm basic requirements

Ensure the Windows Server 2025 machine has:
- Working internet access (test with a browser from that server).
- Required certificates and TLS configuration if using a proxy or SSL inspection.
- Microsoft Visual C++ v14 Redistributable (x86 and x64) if planning an offline layout later.

Try a clean online install/update

Download the latest SSMS 22 bootstrapper (vs_SSMS.exe) from the official SSMS installation page.
Run it once to let it install/update the Visual Studio Installer. If the Choose Workloads page appears, the installer itself is healthy.
If the download still fails with the same internet error, proceed to troubleshooting steps below.

Repair or reset the Visual Studio Installer Online SSMS installs use the Visual Studio Installer engine. If it is corrupted, downloads can fail.

Close the Visual Studio Installer.
Delete the folder:
- C:\Program Files (x86)\Microsoft Visual Studio\Installer
Run the SSMS bootstrapper again (vs_SSMS.exe) to reinstall the Visual Studio Installer and reset installation metadata.
Retry the SSMS installation.

Check for known issues and logs

Review known issues for SSMS/Visual Studio Installer to see if the download problem is a documented issue.
If installation continues to fail:
- Collect logs using the Microsoft Visual Studio and .NET Framework log collection tool (collect.exe) as described in the troubleshooting article.
- The tool generates vslogs.zip in %TEMP%. Inspect or provide this to support to see the exact network/HTTP errors during package download.

Use “Download all, then install” (semi‑offline) If the server’s internet is slow or unstable but still reachable:

Run vs_SSMS.exe on the server.
In Visual Studio Installer, choose SSMS components and then select Download all, then install from the dropdown next to Install.
This downloads all required packages locally first; installation then runs from the local cache, reducing sensitivity to intermittent connectivity.

Fully offline layout (if server has no internet) If the server truly has no internet access:

On a different machine with internet, use the command line to create a local layout with vs_SSMS.exe as described in the offline installation article.
Copy the layout folder to the Windows Server 2025 machine.
Install SSMS from the layout using vs_SSMS.exe --noWeb so it does not attempt any online download.

If issues persist

Verify that corporate firewalls/proxies are not blocking Visual Studio/SSMS endpoints.
If still failing after the above steps, collect logs with collect.exe and open a case or use Report a problem from the Visual Studio Installer for case‑by‑case analysis.

References:

Share via

Setup issue to SQL Server Management studio installer 22

2 additional answers

Your answer