Microsoft Store install blocked on Windows ARM64 (Even though it runs [slowly emulated] if downloaded from internet

[Samuel12321]

Please answer the following questions for yourself before submitting an issue

• Filters were updated before reproducing an issue
• I checked the knowledge base and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

7.22 (Latest store version)

Browser version

Na

OS version

Windows 11 25h2

Traffic filtering

• yes, I do

Ad Blocking

No response

Privacy

No response

Social

No response

Annoyances

No response

Security

No response

Other

No response

Language-specific

No response

Which DNS server do you use?

DNS protection disabled

DNS protocol

None

Custom DNS

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

Steps to reproduce:

1. On a Windows 11 ARM64 device (tested: Surface Pro 11, 25H2), open Microsoft Store
2. Install AdGuard for Windows
3. Download completes, Store launches installer
4. Error appears: “This version of AdGuard from the Microsoft Store doesn’t support ARM64 yet”
5. Check Start menu and Settings → Apps ->Installed apps
6. Adguard appears as an installed app
7. Attempt to launch app - same error appears.

Expected Behavior

The Store allows install to proceed (ideally ARM64 native, or at least x64 emulation as you get with the current web installer).

Failing that a less worse situation would be:
The Store blocks download / installation up-front with a compatibility message and does not create Start menu / Installed Apps entries.

Actual Behavior

Store downloads but blocks the installer at launch with the ARM64 error
AdGuard still appears installed in Start + Installed apps
Launching it only re-shows the error
Must be manually uninstalled to clean it up

Screenshots

Screenshot 1

Additional Information

No response

[Samuel12321]

One possible way to avoid the “installed but not runnable” state in the future (independent of the ARM64 compatibility itself) may be to give the Store build an MSIX identity (e.g. via a sparse package or similar) rather than a brokered EXE install. That would allow the Store/OS to own architecture gating, registration, and uninstall/rollback, so if an external component is blocked or fails, no Start menu or Installed Apps entry would be left behind.
With Winget support also possibly being added in future, this could additionally help unify Store, Winget and website installs under a single, consistent lifecycle.