More and more new Windows computers ship with ARM64 processors instead of the x64 chips that have been standard for years. Our customers asked for compatibility, so we're delivering on that.

What's New

Blue Border for Windows now runs natively on ARM64 devices. There's nothing to request and nothing to configure: install Blue Border on an ARM64 device and it works.

We're releasing this as a public preview. We'd like you to try Blue Border on ARM64 devices and tell us what you find — real usage is what shows us which parts are solid and which still need work.

Get Started

There's nothing to configure. To test out the preview, install Blue Border on an ARM64 Windows device the same way you would on any other Windows device, and it runs natively.

Availability

Blue Border is now compatible with 64-bit ARM (ARM64, also called AArch64) devices, which is what all current Windows-on-ARM hardware uses. Supported hardware includes Microsoft Surface Pro 11, Samsung Galaxy Book 4 Edge, HP EliteBook Ultra ("Q" models), and Snapdragon-based Copilot+ PCs.

32-bit ARM (ARM32) is not supported.

Known Limitations

This is a preview, not a finished product. These are the issues we're currently tracking, and more may surface as people start using it.

Protections Not Yet Available on ARM64

• Antikeylogger protection, which blocks malicious software from recording keystrokes, isn't available yet.
• The Always On Driver, a background component that keeps core Blue Border protections running at all times, doesn't work yet.
• The Simple Persistent Driver, another background protection component, doesn't work yet.
• A protection that stops other apps from spying on or interfering with Blue Border's windows isn't available yet.
• Two security checks that block untrusted or low-trust apps from making certain Windows system requests don't work correctly. One of them can be skipped entirely when an app is running in Windows' ARM64 compatibility mode.
• Screen capture permissions fall back to an older, backend-only method. The same protection still applies, but you can't manage it through the newer admin settings screen.

Other Known Issues

• Some apps can freeze and stop responding when running in Windows' ARM64 compatibility mode.
• A background Windows service can crash in certain situations, which may require a restart to fix.
• Reporting on a device's CPU usage doesn't work correctly.
• Reinstalling Blue Border can cause a device to show up twice in device management.
• Some custom app installers can't install directly on ARM64 devices yet.
• Blue Border's built-in diagnostics tool can show a misleading error about a missing S:\ drive.

FAQ

How do I know whether a device is ARM64?

On a Windows device, open Settings, go to System, then About, and check the System type field under Device specifications. ARM64 devices report an ARM-based processor; most Copilot+ PCs with Snapdragon chips are ARM64.

Should we move our team to ARM64 devices now?

Not yet. We encourage you to try Blue Border on ARM64 devices, but we don't recommend migrating your workforce until ARM64 support reaches general availability.

Beyond the Blue Border limitations above, many business applications have their own ARM-specific constraints, separate from anything in Blue Border. Validate your full set of workflows on an ARM64 device before planning a broader move.

When will ARM64 support be generally available?

We anticipate general availability in early 2027, once we've resolved the high-priority issues above.

Does this change anything for our existing x64 devices?

No. Nothing changes for x64 Windows devices.

How do we report a problem or share feedback during the preview?

Send it to support@venn.com. Real usage feedback is the main reason we're opening the preview now, so please tell us what you run into — including anything not listed above.