**store.xrmtoolbox.com not resolving (DNS) — Tool Library fails to initialize**

[moebius247]

XrmToolBox is showing "Tool Library initialization failed" on startup. I've traced this to store.xrmtoolbox.com failing to resolve via DNS — this appears to be a problem with the domain itself, not a local network/proxy/firewall issue.

Steps to reproduce

1. Open XrmToolBox
2. Tool Library fails to initialize with "Tool Library initialization failed"
3. Attempting to browse to https://store.xrmtoolbox.com directly in a browser fails with "This site can't be reached"

Troubleshooting done

I initially suspected this was a corporate network/DNS block on my end, so I tested from multiple angles:

• nslookup store.xrmtoolbox.com on my corporate network → NXDOMAIN (non-existent domain)
• Tested from my mobile phone hotspot (completely outside any corporate network) using dnschecker.org against multiple public DNS resolvers (Google, Quad9, OpenDNS, NextDNS) → fails to resolve on every single one
• By contrast, www.xrmtoolbox.com (the main site) resolves and loads fine

This strongly suggests the DNS record for the store subdomain specifically has lapsed or been misconfigured, since it's failing globally and not just on networks with corporate filtering.

Expected behavior

store.xrmtoolbox.com should resolve and the Tool Library should load normally, as it did a few days ago.

Environment

• XrmToolBox on Windows
• Issue started within the last few days (previously working fine)

Happy to provide additional diagnostics (traceroute, DNS trace, etc.) if helpful. Flagging this since it looks like an infrastructure/DNS issue on the store subdomain rather than anything client-side.

[AlWallHMLR]

I'm also affected by this - really need to install some tools!!

[CPPOpa]

I'm affected too, as are many of my colleagues. The website itself is accessible, but it takes a very long time to load before anything appears on the screen.

[kylebloom-ifgl]

This is being worked on here #1457

[MscrmTools]

Sorry for the inconvenience, odata feed has been removed by Microsoft and I did not anticipated the deprecation (which was some years ago).
A new unsigned version is available that fixes the issue. Signed version will be available only after August 16th