Open-Shell release 4.4.196 introduced ARM64 support. That is different from guaranteeing every later Windows on ARM build will accept every installer. Check the PC architecture, release notes, and the exact wording of any installation block.
What to do
- Open Settings > System > About and confirm that System type identifies an ARM-based processor. A 64-bit label alone does not distinguish ARM64 from x64.
- Read the release notes for the version you intend to use, including any ARM-specific limitations. Keep the Windows build number from winver with your notes.
- Verify the installer asset and published hash before starting setup. When Windows blocks the file, record whether it is a compatibility message or a security-policy message.
- Test the menu with a built-in style after setup. Evaluate Explorer extensions separately instead of assuming that successful menu activation proves every component works.
Check the result
Test Start activation, app launch, settings persistence, and sign-in behavior on the ARM PC. Include architecture and the exact build in any issue report.
Limits & precautions
Project notes include a historical filename workaround for an ARM compatibility block. Do not apply it blindly to Smart App Control, antivirus detection, or a managed-device policy.
Questions & answers
When was ARM64 support introduced?
It is listed in the project notes for 4.4.196.
Is ARM64 the same installer problem as x64?
Not necessarily. Architecture, compatibility blocks, and security policy should be distinguished.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.