Emsisoft System Requirements and Platform Support

Emsisoft compatibility matrix for August 2026

This table uses “endpoint protection” narrowly: software runs on that device and protects it. It doesn't count a browser that can view another machine's status. It also doesn't turn silence into support. Apple silicon is explicitly named; Windows ARM isn't. Android is explicitly a separate product; ChromeOS isn't.

The official matrix and storefront aren't perfectly synchronized. We treat the most specific current primary statement as the floor, expose contradictions, and ask for confirmation where a page says “and higher” while its detailed matrix stops at named versions. That's safer than converting marketing shorthand into a deployment guarantee.

Choose the Emsisoft product before checking the operating system

“Does Emsisoft support this device?” is incomplete because the brand includes four different roles. Anti-Malware Home is resident household protection for Windows and Mac. Business Security and Enterprise Security add organizational management and Windows Server rights. Emergency Kit is a portable Windows scanner, not always-on protection. Mobile Security is a separate Android product.

The plan boundary matters as much as the technical one. A binary that can run on Windows Server isn't licensed as Home protection. A mobile console icon isn't the Android security app. And Emergency Kit can scan a supported Windows machine without replacing Home's resident File Guard/Behavior Blocker job. Our Home versus Emergency Kit guide covers that role split.

Windows 10 and Windows 11: 64-bit and currently serviced

Emsisoft's supported-platform matrix lists 64-bit Windows 10 and Windows 11 for new installations of Home, Business, Enterprise, Emergency Kit and Commandline Scanner. The current Home page shows Windows build 2026.1.0.12700, released February 20, 2026, when checked August 7.

“Windows 10 supported” isn't a promise for every frozen Windows 10 image. Emsisoft says its rule of thumb is the current and previous two Windows 10/11 versions—about 18 months, similar to Microsoft's servicing policy. Check `Settings → System → About` and `winver`, then compare the exact edition/version with Microsoft's active lifecycle. Install all current quality/security updates before judging antivirus compatibility.

New Windows installations must be 64-bit. The alternative MSI contains only 64-bit files and is roughly 340 MB; the small web installer downloads components. A Store-only “Microsoft-verified app” restriction is a Windows policy/source check, not evidence the processor or OS is unsupported. Use the current signed installer from the intended MyEmsisoft workspace as described in our installation guide.

Windows S mode isn't explicitly listed as a supported Emsisoft configuration. Since S mode normally limits installations to Microsoft Store apps, don't disable it merely because a third-party article says Emsisoft works on Windows 11. Verify the exact edition and security policy first; switching out of S mode is a separate and effectively one-way Windows decision.

Windows on ARM isn't confirmed by the words “64-bit Windows”

Windows ARM64 is a 64-bit operating system, but that doesn't make every x64 security driver compatible. Antivirus products depend on kernel services, network filtering and self-protection—not just an ordinary application process. Emsisoft explicitly names Intel and Apple silicon for Mac, yet its current Windows pages don't explicitly say ARM64, Snapdragon or Windows on ARM.

We therefore mark Windows ARM unconfirmed, not categorically impossible. Don't use x64 emulation support for ordinary desktop apps as proof that a resident antivirus will work correctly. Before buying, send Emsisoft the exact device model, processor, Windows edition/build and intended plan and ask whether the current endpoint agent and every protection driver are supported.

If you already installed it, verification must go beyond “the window opens.” Check protection status, updates, services, web filtering, a safe test workflow and MyEmsisoft reporting after restart. Preserve any driver/installation error. Don't disable Windows protections, Memory Integrity or other platform security to force an unsupported third-party build.

macOS 11+ now has a current Emsisoft Home agent

This is the biggest platform change older reviews miss. The current Home and Business Security pages list macOS 11 Big Sur and later on Intel and Apple silicon, with Mac build 2026.2.0.785 when checked. A 2025 beta announcement is historical context, not the current product status.

Apple silicon support is explicit and not limited to one named M-series generation. Still, the OS floor matters: an M-series Mac on an unsupported or damaged macOS build isn't made ready simply by having the right CPU. Use the workspace's current Mac download, follow the live installer/System Settings prompts, then verify device visibility, updates and protection after a restart.

Don't copy Windows assumptions onto Mac. Product availability doesn't prove feature parity, identical local controls or identical independent-lab coverage. Emsisoft's early beta page documented remote-only management and several Mac limitations; current pricing/features should be used for present capability decisions, while the public Home page establishes only that the current Mac agent exists and what OS/CPU families it supports.

For a managed Mac fleet, test the actual macOS release, privacy permissions, network extension/content-filter behavior and MDM profile before broad deployment. A single successful manual install on one Intel Mac doesn't validate an Apple-silicon fleet, and vice versa.

Android uses a separate Mobile Security product—and its minimum is contradictory

The current Mobile Security page lists version 16.4.5, released July 14, 2026, and says Android 5.0 and up. The general supported-platform matrix repeats Android 5.0+. But the newer Mobile Security user guide says Android 7.0 or later and requires internet for cloud-based protection.

We can't honestly collapse those statements into one exact minimum. For purchase/deployment, use Android 7.0+ as the safer operational floor and let the current Google Play listing on the exact phone/tablet decide install compatibility. If a 5.x/6.x device still accepts the app, that doesn't mean the vendor intends full current functionality or long-term support.

Mobile Security isn't the Home desktop agent shrunk for a phone. It has its own subscription/activation route and Android-specific permissions for cloud scanning, web protection, anti-theft and other features. Check OS version, Google Play availability, internet access and permissions on the real device. Avoid APK mirrors; an antivirus APK is an especially poor file to source outside the official store.

The Android app and MyEmsisoft/Management Console are also separate. Opening a console PWA on Android can manage Windows/Mac endpoints without installing Mobile Security on that phone. Conversely, buying Mobile Security doesn't silently add a Home seat for a PC.

iPhone and iPad can manage Emsisoft, but no iOS antivirus agent is listed

Emsisoft says its Management Console can be opened from a browser or pinned as a Progressive Web App on iOS using Safari and Add to Home Screen. That gives an administrator a convenient view of other protected endpoints. It doesn't scan iOS apps, add a local File Guard or turn the iPhone into a protected Emsisoft endpoint.

The current product list and contact form name Mobile Security as Android. No current Emsisoft iPhone/iPad antivirus product is listed. So “Emsisoft has an iOS app” is true only in the management-console/PWA sense and misleading if used as a cross-platform protection claim.

For an Apple household, a Home license can cover supported Windows and Mac PCs while an iPhone opens the console. That may still be useful, but it isn't the same as a suite that provides a dedicated iOS web/privacy component. Buy based on the protected endpoints you actually need, not the number of icons that can appear on a home screen.

Linux and Chromebook: console access isn't local endpoint support

Emsisoft's current Home, Business, Enterprise and supported-platform pages don't list a Linux endpoint agent. A Linux computer may open MyEmsisoft in a compatible browser, but that only accesses the cloud console. It doesn't install Emsisoft scanning, behavior monitoring or web filtering on Linux.

ChromeOS/Chromebook is also absent from the endpoint matrix. Some Chromebooks run Android apps through Google Play, but Android-app availability on a ChromeOS device isn't a vendor statement that Mobile Security protects the ChromeOS host, browser, Linux container or every Android subsystem. Don't infer full Chromebook protection from store compatibility alone.

Emergency Kit and Commandline Scanner aren't Linux fallbacks. EEK is a supported-Windows portable scanner, and the current command-line product page names Windows/Mac/Server contexts rather than a Linux binary. For mixed fleets, pair Emsisoft only with the platforms it explicitly covers and choose another supported control for Linux/ChromeOS instead of leaving those endpoints in a documentation gap.

Windows Server needs Business or Enterprise—not Home

The detailed English matrix names 64-bit Windows Server 2016, 2019 and 2022 for Business Security and Enterprise Security. The current Business product page uses the broader phrase “Server 2016 and higher.” Because the specific matrix doesn't yet name Windows Server 2025, we would confirm that exact release with Emsisoft before a production rollout rather than treating “and higher” as a blanket certification.

Home isn't a server license. Current Emsisoft pricing says Business protects Windows servers and clients with no separate server license needed, while the feature matrix places Windows Server OS support in Business/Enterprise. Choose the organizational plan even if the Home installer seems technically capable of starting on a server.

Server testing must include boot-without-user protection, file shares, connected storage, backup/line-of-business workloads, management reporting and maintenance windows. A file server failure has a different blast radius from a home laptop, so “supported OS” is only the first deployment gate.

Windows 32-bit, 8.1, 7, XP and old Server releases aren't new-install targets

Emsisoft explicitly lists Windows 10 32-bit, Windows 8.1, Windows 7, Windows XP, Server 2012/R2 and Server 2008 R2 as unsupported for new installations. The page says existing installations no longer receive monthly software feature updates, although malware-detection updates may continue until further notice.

“Detection updates still arrive” isn't equivalent to a supported security posture. An obsolete OS can lack platform patches, modern browser protections and current driver compatibility; an antivirus can't repair the operating system's lifecycle. Don't preserve an old machine in production because one Emsisoft component still downloads signatures.

If a legacy computer must be accessed for recovery, isolate it, minimize network exposure, copy data through a controlled process and plan replacement. Emergency Kit can be useful for a supported Windows cleanup job, but it isn't a license to reconnect an unsupported workstation indefinitely.

RAM, disk, CPU and internet: current public minimums are incomplete

The live Home page and supported-platform matrix provide OS/architecture boundaries but don't publish a fresh, comprehensive RAM, processor or free-disk minimum. Search results surface old 2020 datasheets with 2 GB RAM language; we don't treat those as a 2026 guarantee for current builds, signatures, browsers or macOS agents.

Use the supported operating system's practical hardware floor as the beginning, not the target. Leave headroom for the roughly 340 MB Windows MSI, installed components, signature updates, quarantine, reports and temporary files. An SSD, current CPU and enough RAM to run the OS and everyday workload without constant paging matter more than hitting an inherited brochure number.

Internet access is operationally required for download, activation, MyEmsisoft connection, cloud intelligence, updates and Mobile Security cloud scanning. Proxies and restrictive firewalls need current vendor endpoints/ports. A laptop that can install offline but can't update or report isn't a successful deployment.

Measure on the target machine: clean boot baseline, idle memory/CPU, first update, Malware Scan, normal browsing/workload and restart. Performance problems belong in the dedicated Emsisoft troubleshooting spoke; compatibility decisions shouldn't invent universal resource numbers from one computer.

Virtual machines and cloned images need unique identity, not just compatible Windows

A Windows 10/11 x64 VM can meet the OS statement while still failing licensing or console identity. Emsisoft's enhanced-license guidance says cloned images may cause Managed Devices and Used Devices to differ and tells administrators to generalize with Sysprep. A clone that carries another endpoint's identity isn't a clean new device.

Prepare a generalized image before connecting it with a workspace-specific token. Never capture a public/golden image that contains a permanent tagged installer, active license identity or live endpoint record. After deployment, verify every clone has a distinct device entry and expected seat usage.

VDI, snapshots, non-persistent pools and nested/emulated processors introduce churn that the basic public platform page doesn't certify. Ask Emsisoft about the exact virtualization lifecycle and licensing model before scale. Repeated hardware identity changes can also encounter the documented mapping limit, so a lab that constantly reverts snapshots needs a deliberate design.

Protection isn't the same as Management Console access

The console is part of MyEmsisoft and can be used through a web browser or pinned as a PWA on Windows, macOS, iOS and Android. That broad access is an administration feature. The protected endpoint list is narrower: current Windows/Mac agents, separate Android Mobile Security and plan-qualified Windows Server.

This distinction resolves several misleading search phrases. “Emsisoft for iOS” may point to console access. “Emsisoft app for Android” may mean either Mobile Security or the console PWA. “Emsisoft works on Linux” may mean the site opens in a browser. Always ask whether code runs locally to protect the device or merely displays another endpoint's state.

For console access, use a current browser, secure MyEmsisoft account and second factor. For endpoint support, use the signed platform-specific agent, compatible OS/architecture, correct plan and local verification. Those are two separate checklists.

Use this pre-purchase and pre-deployment compatibility check

1. Name the job. Resident protection, portable scan, Android mobile protection or remote console?
2. Name the product. Home, Business, Enterprise, EEK or Mobile Security?
3. Record the exact OS. Edition, version/build, 32/64-bit and current servicing status.
4. Record the processor. Intel/AMD x64, Apple silicon or Windows ARM.
5. Check the explicit matrix. Don't turn browser access or “and higher” into an unqualified endpoint promise.
6. Check plan rights. Server and organizational use require the correct edition.
7. Check the real store/installer. Especially Android and Mac workspace downloads.
8. Pilot and verify. Install, update, restart, confirm local status, workspace identity and normal workload.

If the exact platform is absent or documentation conflicts, contact Emsisoft before paying and save the answer with the date/build. Our current Emsisoft review evaluates the product itself; our pricing guide covers plan and term. This page answers only whether the intended device and role have a defensible support path.