Unable to open a specific link from one of the computers in the organisation

Hi Spoorthy,

It seems the failure is almost certainly tied to the Windows network stack or device-level policy rather than the browser. At this point I would verify whether the system can resolve and reach the destination by running nslookup <URL-domain> and Test-NetConnection <URL-domain> -Port 443 in PowerShell to confirm DNS resolution and TLS connectivity; compare the resolved IP with a working machine. If DNS differs, check for a device-level override such as NRPT rules (Get-DnsClientNrptPolicy) or a custom DNS suffix configuration under HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

If DNS resolves correctly but HTTPS fails, inspect the Windows certificate trust store and TLS configuration, especially certlm.msc → Trusted Root Certification Authorities and the SCHANNEL settings under HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL, as corrupted or missing roots can block specific sites. Another common device-specific cause is Windows Defender Application Control / SmartScreen / enterprise filtering, which can silently block certain domains; check Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity and Windows Defender.

And please also confirm the NIC is not using a stale static DNS server (Get-DnsClientServerAddress) that differs from the organization standard. If all checks are normal, capture the exact browser error and test curl https://<domain> from PowerShell to determine whether the failure is DNS, TCP, or TLS before considering an in-place Windows repair (setup.exe /repair) of the OS image.

I hope it works. If it's helpful to you, please give it a thump up or accept the answer, very appreciate it :)

Harry.

Based on the steps already taken, the issue is very likely specific to this Windows installation or its network stack rather than the browser, user profile, or physical network.

Given the constraints (cannot install external tools or disable security), these are the remaining actions that align with documented guidance and similar cases:

1. Verify Edge can reach required endpoints
   Since the primary browser is Microsoft Edge and the issue is with a specific site, ensure that required Edge endpoints are not being blocked on this device (by local security software, local firewall, or a misapplied policy):
   • Confirm that https://msedge.api.cdp.microsoft.com and *.dl.delivery.mp.microsoft.com are not blocked, as these are used by Edge for updates and downloads and can indicate broader connectivity filtering on this device.
   • If your organization uses allow/block lists, compare this device’s effective policy with a working device.
2. Check third‑party security software on this device
   Even if all machines are imaged the same way, this one device may have:
   • A corrupted or outdated local security agent, or
   • A different policy version applied.
     On the affected PC:
   • Open any third‑party security/AV client (for example, Norton, McAfee, or an enterprise agent) and check for updates.
   • If allowed, trigger a repair or policy refresh from the security console or ask the security/admin team to redeploy the agent to this machine.
3. Clear all Edge browsing data (not just cookies)
   You already cleared cookies; also clear all cached data:
   • In Edge: Settings and more > History > Open history page > Delete browsing data.
   • Set Time range to All time, select all boxes (including cached images/files and site permissions), then Clear now.
     Test the problematic site again.
4. Test with another browser + another site from this device
   You already tried a different browser for the specific link. Also verify:
   • Whether other HTTPS sites (especially those using modern TLS) work consistently from this device.
   • If multiple unrelated sites fail similarly, this reinforces a local network stack or security agent issue.
5. Reset the Hosts file to default
   You checked that the hosts file does not explicitly block the link; if allowed, reset it fully to the Windows default to rule out hidden or malformed entries:
   • Follow the documented procedure to reset the Hosts file back to default for Windows 11/10.
   • Reboot and test the site again.
6. Run the full TCP/IP and Winsock reset sequence once more
   The documented sequence for fixing Ethernet issues is:
   1. Open Command Prompt as administrator.
   2. Run, in order:
      • netsh winsock reset
      • netsh int ip reset
      • ipconfig /release
      • ipconfig /renew
      • ipconfig /flushdns
   • Restart the PC and test both Ethernet and Wi‑Fi with the problematic site.
7. Compare behavior on Wi‑Fi vs Ethernet again
   You already tested both, but after the above steps and any security‑agent refresh:
   • Test on Wi‑Fi and Ethernet again.
   • If both still fail only on this device while another laptop on the same cable works, it further isolates the problem to OS or local security configuration.
8. Escalate with device‑specific reimage or support
   Since all devices are imaged the same way and you cannot install tools or disable security, and you have already rejoined the domain, the remaining realistic remediation is:
   • Have IT reimage this specific PC from the standard corporate image, or
   • Open a support ticket with your internal IT or Microsoft support, referencing that another machine on the same network path works and that full TCP/IP reset, Edge repair steps, Hosts reset, and domain rejoin have been attempted.

These steps align with Microsoft’s guidance for Edge/network issues and host file/network stack problems and are the main remaining actions possible without third‑party tools or policy changes.

References:

• Troubleshooting tips for downloading, installing, and updating Microsoft Edge
• What to do if Microsoft Edge isn't working
• Fix Ethernet connection problems in Windows
• How to reset the Hosts file back to the default