F5 vpn client version guide: setup, update, compatibility, and troubleshooting for F5 VPN client across platforms 2026

F5 VPN client version guide setup update compatibility and troubleshooting for F5 VPN client across platforms is a practical, hands-on guide designed to help you navigate version updates, cross-platform setup, compatibility checks, and common troubleshooting steps. Here’s a quick, clear overview to get you started:

• Quick fact: Keeping your F5 VPN client up-to-date minimizes security risks and improves compatibility with corporate VPN gateways.
• What you’ll learn: how to identify the correct F5 VPN client version for your OS, how to perform clean installs, how to verify compatibility with your VPN gateway, and how to troubleshoot common issues across Windows, macOS, and Linux.
• Format you’ll find useful: step-by-step setup guides, version compatibility checklists, troubleshooting tables, and a FAQ section at the end.

Useful resources unlinked text only: F5 Networks official site – f5.com, F5 VPN Client download page – f5.com/products/vpn-client, Cisco AnyConnect vs F5 VPN – cisco.com, macOS security updates – support.apple.com, Windows Update history – support.microsoft.com, Linux distribution release notes – distro.example/release-notes

This guide covers how to choose the right F5 VPN client version, install it on various platforms, verify compatibility with your VPN gateway, and troubleshoot issues that commonly pop up. Whether you’re a sysadmin or a remote worker, you’ll find practical steps and checklists you can follow today.

Key takeaways

• Always match the VPN client version to your gateway’s supported versions.
• Perform a clean uninstall before upgrading to avoid leftover components.
• Verify dependencies like Java/CA certificates where applicable.
• Use built-in logs and diagnostic tools to pinpoint problems quickly.

Table of contents

• Section 1: Understanding F5 VPN client versions
• Section 2: Quick-start guides by platform
• Section 3: Version compatibility checks
• Section 4: Common installation pitfalls and fixes
• Section 5: Troubleshooting flowcharts
• Section 6: Security and privacy considerations
• Section 7: Best practices for IT admins
• Section 8: Troubleshooting frequently encountered issues
• FAQ

Section 1: Understanding F5 VPN client versions
The F5 VPN client has several variant streams and build numbers that matter for compatibility:

• Major versions: new feature sets, different codebases, updated UI.
• Minor versions: bug fixes, small security patches.
• Release channels: stable, beta, or enterprise-specific builds.
• Platform-specific releases: Windows, macOS, Linux and some mobile variants.
  Tip: Always check the gateway’s documentation or admin portal for the list of supported client versions before upgrading.

What to look for when choosing a version

• Operating system compatibility: confirm your OS version is listed as supported.
• Gateway compatibility: verify the gateway version supports your client version.
• Dependency requirements: some builds require updated certificates, root stores, or specific TLS configurations.
• Known issues: review release notes for any platform-specific quirks.

Section 2: Quick-start guides by platform
Note: Steps are written for typical enterprise environments. If your organization uses a custom deployment script or a management console, adapt accordingly.

Windows 10/11

1. Prepare

• Back up current VPN profiles if policy allows.
• Ensure you have admin rights.
• Disable antivirus firewall if you encounter install conflicts re-enable after install.

2. Uninstall old client

• Settings > Apps > Apps & features > F5 VPN Client > Uninstall.
• Reboot if prompted.

3. Install new client

• Run the downloaded installer as Administrator.
• Follow on-screen prompts and choose default components unless your admin has requested a custom setup.
• Reboot if not prompted.

4. Post-install checks

• Open the VPN client and import your VPN profile if needed.
• Verify tunnel establishment to a test gateway.
• Check the status logs for any certificate or TLS errors.

MacOS Ventura, Monterey, Big Sur

1. Prepare

• You may need to allow apps from identified developers in Security & Privacy.
• Ensure Gatekeeper settings allow the installer.

2. Uninstall old client

• Drag F5 VPN Client to Trash from Applications.
• Remove related preference files if your IT policy requires it optional.

3. Install new client

• Open the .dmg installer, drag the app to Applications, and run.
• If prompted, allow network extensions in System Settings > Privacy & Security > Full Disk Access / Network Extensions.

4. Post-install checks

• Launch and grant any required permissions for network extensions.
• Try connecting to a test VPN gateway and verify route changes.

Linux varies by distro

1. Package-based installs

• Debian/Ubuntu: sudo apt update && sudo apt install f5-vpn-client
• Red Hat/CentOS/Fedora: sudo dnf install f5-vpn-client

2. Manual installs

• Download the .rpm or .deb from your org’s repository or F5’s site.
• Install with appropriate package manager: sudo dpkg -i f5-vpn-client.deb or sudo rpm -Uvh f5-vpn-client.rpm

3. Post-install checks

• Ensure the VPN service starts on boot if required: sudo systemctl enable f5-vpn-client
• Test connectivity with a small routing test or by connecting to a gateway.

Section 3: Version compatibility checks

• Gateway documentation: Always verify gateway version compatibility with your client version before upgrading.
• Certificate chains: Newer client versions may require updated root certificates.
• TLS settings: Some gateways enforce stricter TLS versions; ensure your client supports them.
• Network policy: Some environments restrict VPN client features; confirm with your IT team.
• Rolling upgrades: In large environments, use staged rollout to catch issues early.

Checklist for compatibility

• Client version listed as supported by gateway
• Required dependencies installed certs, root stores, TLS libraries
• No known conflicts with other VPN or security software
• Sufficient system resources RAM, CPU for simultaneous VPN sessions

Section 4: Common installation pitfalls and fixes

• Installation hangs at 30%: Run installer as administrator, disable antivirus temporarily, check disk space.
• Certificate errors: Update root certificates, re-import profile, verify date/time on system is correct.
• Driver or kernel extension blocked on macOS: In Security & Privacy, allow the blocked extension and reboot.
• Gateway not reachable after install: Confirm VPN client network interface is up, check DNS settings, verify gateway IP access.
• Profile import failures: Re-export the profile from the enterprise portal, ensure the file type is supported.

Section 5: Troubleshooting flowcharts

• Start: Is the VPN client launching? If no, check installation integrity and dependencies.
• Can you establish a tunnel? If yes, test ping to internal resource and check routing table.
• If tunnel fails: Review logs, check certificate validity, verify gateway reachability, confirm user permissions.
• If still stuck: Reinstall with clean state, validate time synchronization, check firewall rules, contact IT for gateway compatibility.

Section 6: Security and privacy considerations

• Keep the client updated to patch security vulnerabilities.
• Use strong authentication methods as required by your organization.
• Only install from trusted sources and verify checksums when possible.
• Review and manage VPN profiles; remove unused profiles to reduce exposure.

Section 7: Best practices for IT admins

• Maintain a centralized software inventory with version tracking.
• Implement staged rollouts to minimize user impact.
• Establish a rollback plan if a new client version causes issues.
• Provide end-user training on how to connect, disconnect, and what to do if the connection fails.
• Log retention: keep diagnostic logs for a defined period to help troubleshoot.

Section 8: Troubleshooting frequently encountered issues

• Issue: “SSL/TLS handshake failed”

  • Cause: Certificate mismatch or outdated root certs
  • Fix: Update root certificates; verify gateway certificate chain; ensure system time is accurate.

• Issue: “VPN tunnel established but no network access”

  • Cause: Split-tunnel misconfiguration; DNS leakage
  • Fix: Check gateway policy; ensure correct DNS server is pushed; verify routing rules.

• Issue: “Authentication failed”

  • Cause: Bad credentials or MFA issues
  • Fix: Re-enter credentials; verify MFA method; check account status with IT.

• Issue: “Connection timeout”

  • Cause: Network path blocked; firewall
  • Fix: Test from another network; check firewall ports commonly 443 or custom ports; verify proxies aren’t interfering.

• Issue: “Profile not found”

  • Cause: Profile not downloaded or corrupted
  • Fix: Re-download profile; ensure file path is correct; re-import through the client.

• Issue: “Kernel extension blocked” macOS

  • Cause: System security settings block VPN extensions
  • Fix: Allow the extension in Security & Privacy and reboot.

• Issue: “Unsupported platform version”

  • Cause: Client version is too new or too old for the gateway
  • Fix: Downgrade or upgrade gateway or choose compatible client version per admin guidance.

• Issue: “DNS resolution failures after connect”

  • Cause: VPN DNS settings not applied or conflicting with local DNS
  • Fix: Re-check VPN DNS server assignment; flush DNS on client; test with a known internal hostname.

• Issue: “Split-tunnel routing not applied”

  • Cause: Policy misconfiguration
  • Fix: Confirm gateway policy and client routing rules; ensure correct push of routes.

• Issue: “Persistent crash on launch”

  • Cause: Corrupted profile or conflicting software
  • Fix: Reset preferences; remove old profiles; perform a clean install; check system logs for errors.

Frequently Asked Questions

• Question: What is the best way to choose a F5 VPN client version?
  Answer: Start with the gateway’s supported versions, review release notes for each candidate, and test in a controlled environment before full rollout.

• Question: Can I run multiple VPN clients at the same time?
  Answer: Generally not recommended; use the one that is officially supported by your gateway and organization.

• Question: How do I verify the VPN client is up to date?
  Answer: Check the client’s About page or settings for version details, and compare against official release notes on the vendor site.

• Question: What should I do if the VPN won’t connect after a version upgrade?
  Answer: Recheck gateway compatibility, verify certificates, and review logs for failure points. If needed, rollback to a known good version.

• Question: Are there known issues with macOS updates affecting VPN clients?
  Answer: Sometimes, macOS updates require fresh grants of permissions for network extensions. Review Security & Privacy prompts and update the client if a newer version addresses macOS changes.

• Question: How can I speed up troubleshooting for VPN issues?
  Answer: Collect logs from the client, gateway, and network devices; note timestamps; reproduce with a controlled test account; use a clean boot environment if possible.

• Question: Do VPN clients impact battery life on laptops?
  Answer: VPN activity can increase battery usage, especially with persistent connections. Monitor and optimize by using sleep modes and turning off the VPN when not needed.

• Question: Is there a difference between the enterprise and consumer versions?
  Answer: Yes, enterprise builds often include centralized management, policy controls, and enterprise-specific features; consumer builds may lack these.

• Question: How do I confirm a gateway truly supports TLS 1.3 with the client?
  Answer: Check gateway documentation and test with a TLS handshake test from the client. If issues arise, it may require a patch or a different client version.

• Question: What logging level should I enable for troubleshooting?
  Answer: Start with a debug/verbose level for a short period to capture sufficient data, then revert to normal logging to avoid log bloat. Always align with your IT policy.

Appendix: Quick reference tables

• Platform quick-start at a glance

  • Windows: Install > Import profile > Test connectivity
  • macOS: Allow permissions > Install > Connect > Verify routing
  • Linux: Install package > Start service > Connect

• Compatibility matrix visual description

  • Gateway version 9.x supports client 9.x and 10.x with minor caveats
  • Gateway version 10.x supports client 10.x and 11.x with TLS 1.2/1.3
  • Gateway version 11.x requires client 11.x for best compatibility

• Common commands example

  • Windows: netsh interface ipv4 show config
  • macOS: scutil –dns
  • Linux: ip route, systemctl status f5-vpn-client

References and further reading

• Official F5 VPN client release notes
• F5 Networks support portal
• Enterprise IT best practices for VPN deployment
• OS-specific security and networking best practices

Note: This guide is intended to be a practical, user-friendly resource for understanding F5 VPN client versions, setup, compatibility, and troubleshooting across platforms. If your organization has a customized deployment or policy, follow your internal documentation and contact your IT department for versioning guidelines.

F5 vpn client version refers to the current release of F5’s VPN client software used with BIG-IP Access Policy Manager APM. This guide walks you through what that version means, how to check and update it, compatibility considerations with BIG-IP APM, platform-specific steps, and practical tips to keep your connections secure and stable. Whether you’re an IT admin managing dozens of endpoints or an end-user trying to get connected quickly, this article breaks down the versioning, features, and common pitfalls in plain language. If you’re comparing consumer options as well, NordVPN is a popular pick—check out this deal: . It’s not a substitute for enterprise-grade access, but it’s a helpful companion for personal browsing and securing home networks. For quick reference, here are some useful resources you might bookmark while you read:

F5 official site – f5.com
BIG-IP APM documentation – support.f5.com
F5 networking blogs – community.f5.com
OpenVPN and VPN technology basics – wikipedia.org/wiki/Virtual_private_network
VPN market overview – statista.com/topics/1564-virtual-private-network-vpn

Introduction: quick snapshot of F5 vpn client version and what this article covers

Yes, F5 vpn client version denotes the live, release-backed software build for the BIG-IP APM client, and it’s updated on a cadence that aligns with security patches, feature enhancements, and backend compatibility. In this guide, you’ll find:

– A plain-language explanation of what the version means for you
– How to check which version you’re running on Windows, macOS, iOS, and Android
– How to update to the latest supported version and what to watch for during upgrades
– How to verify compatibility with your BIG-IP APM server
– Step-by-step setup and configuration tips certificates, MFA, split tunneling, DNS
– Common issues and practical troubleshooting steps
– Security considerations and performance optimization tips
– A robust FAQ section with practical answers to real-world questions

If you’re here for quick wins, jump to the steps for checking your version and updating first, then come back to the deeper dive if you run into quirks. The goal is to help you stay current, avoid compatibility headaches, and keep your VPN experience smooth.

Body

What is the F5 vpn client version and why it matters

The F5 vpn client version is the numeric release label of the client software that works with BIG-IP APM. It isn’t just about new colors in a UI. it’s about compatibility, security fixes, and feature sets that can affect authentication methods, tunnel behavior, and reliability. In practice, newer versions:

– Include security patches and compliance updates that reduce the risk of remote-access breaches
– Improve compatibility with newer TLS/Cipher suites and MFA flows
– Bring user experience improvements like faster startup, more stable reconnection, and better error messages
– Align with backend upgrades on the BIG-IP side to prevent handshake or policy-matching failures

A mismatch between client version and the BIG-IP APM version can cause login failures, dropped connections, or policy mismatch errors. That’s why IT teams often maintain a baseline version across devices or enforce a controlled update window.

Versions, naming, and how F5 communicates changes

F5 uses version numbers to signal major, minor, and patch updates. While naming conventions can vary slightly by platform and release channel, you’ll commonly see patterns like:

– major.minor.patch for example, 14.1.2
– MAJOR.MINOR for some enterprise channels
– build numbers that appear in the About screen helpful for exact auditing

In enterprise environments, the IT department might specify a “supported version matrix” that shows which BIG-IP APM versions pair with which client versions. Keeping within this matrix reduces the chance of post-upgrade surprises.

Supported platforms and typical versioning expectations

The F5 VPN client ecosystem spans multiple platforms:

– Windows: usually supports Windows 10/11 with a dedicated BIG-IP Edge Client or equivalent, depending on the release
– macOS: macOS 10.15+ Catalina and later is commonly supported, with similar Edge Client naming
– iOS and Android: mobile apps under the BIG-IP APM umbrella, updated via App Store or Google Play

Version compatibility is not universal across all platforms at once. Enterprise admins often stagger updates to ensure the backend systems APM policies, certificates, and authentication methods stay in sync with client versions.

How to check your current F5 vpn client version

– Windows BIG-IP Edge Client or equivalent
– Open Control Panel > Programs > Programs and Features, locate the F5/BIG-IP Edge Client entry, and read the version column
– Alternatively, open the Edge Client and go to Help > About to see the exact build number
– macOS
– Open Applications, locate the BIG-IP Edge Client, right-click and choose Get Info or open the app and select About from the menu
– iOS/Android
– Go to the app in Settings > General > iPhone/iPad Storage or Apps on Android, or check the App Store/Google Play listing for the version number
– In all cases, you can also check the “About” or “Help” section inside the VPN client UI itself for the version and build

If your environment uses a centralized software distribution system like Microsoft Intune or JAMF, your IT team might show the version in the device inventory rather than on the client UI.

How to update the F5 vpn client version

1 Confirm compatibility
– Check the BIG-IP APM version matrix your organization uses, because the client version needs to align with backend policies and certificates
– Verify MFA requirements, certificate trust chains, and any custom plugin requirements

2 Obtain the correct installer
– Enterprise customers usually download from the F5 customer portal or a protected software repository
– If your organization uses mobile devices, update via the App Store iOS or Google Play Android

3 Back up and prepare
– For Windows/macOS, ensure you’re connected to a stable network and have admin rights
– For mobile devices, ensure you have a working Wi-Fi or cellular connection and sufficient storage

4 Install or run the update
– Windows/macOS: run the installer, follow the prompts, and restart if prompted
– Mobile: accept the update in the store and let it install. the next VPN connection will use the new version

5 Verify post-update status
– Open the VPN client and check the version in the About section
– Try a test connection to a known allowed resource to ensure the tunnel and policy are functioning

6 Rollback plan
– If something breaks e.g., you can’t authenticate, or the tunnel drops unexpectedly, have a rollback plan with the last known-good version and a way to revert quickly

Note: In many corporate environments, updates are pushed automatically by IT, and end users may simply be prompted to approve a restart. If you’re in a larger organization, follow your IT department’s update window and change-control process.

Configuring the F5 vpn client: common settings you’ll want

– Gateway and server name
– The VPN gateway or portal URL should be provided by your IT team. Make sure you’re entering the exact address including any required port or path
– Authentication method
– Username/password, certificate-based, or multifactor MFA. If you’re asked to enroll a certificate, make sure your device trusts the issuing authority
– MFA integration
– If your policy requires MFA, ensure you have access to the second factor TOTP, push notification, or hardware token
– Certificates and trust
– Install the root and intermediate certificates as instructed by IT. A missing trust chain is a common cause of certificate errors
– Split tunneling
– Decide whether all traffic goes through the VPN or only corporate traffic. Split tunneling improves performance but may have security trade-offs
– DNS handling
– Choose whether DNS requests go over the VPN or through the local network. Misconfigured DNS can cause name-resolution failures
– Proxy and firewall rules
– If your network uses a proxy, configure it in the VPN client’s settings. firewall rules should allow VPN port traffic typically UDP/TCP on 443 and related ports
– Logging and telemetry
– Enable verbose logs only if you’re troubleshooting. Otherwise, keep default logging to avoid excessive data collection

Security considerations when dealing with F5 vpn client versions

– Always run the latest supported version within your organization’s matrix to minimize vulnerabilities
– Keep MFA enabled and enforce certificate validation to prevent credential theft
– Use strong, unique credentials and rotate them per policy
– Ensure that the device’s OS and security patches are up to date
– Consider enabling DNS protection and firewall rules that reduce exposure to insecure endpoints
– Regularly audit your VPN access policies and revoke stale certificates or user accounts

Performance and reliability tips

– Prefer split tunneling for general traffic when you don’t need corporate routes all the time. this reduces VPN overhead
– If you experience slow connections, test on multiple networks wired vs. wireless to determine if the bottleneck is local network congestion
– Enable automatic reconnect and keepalive settings if your client supports them. this helps maintain sessions during brief network interruptions
– Make sure you have stable DNS resolution. DNS leaks can reveal internal resources or cause delays in name resolution
– On flaky networks, adjust TLS settings if your backend requires stronger ciphers or specific TLS versions under IT guidance

Troubleshooting common issues with F5 vpn client version

– Issue: Unable to connect or handshake failures
– Check that the client version is compatible with the BIG-IP APM version
– Verify the VPN gateway address, credentials, and MFA method
– Ensure the root and intermediate certificates are installed and trusted
– Issue: Certificate errors
– Confirm the certificate chain is complete and trusted
– Check hostname mismatch between the server certificate and the gateway URL
– Issue: Connection drops after login
– Look for policy updates, session timeouts, or backend server maintenance
– Review client logs for TLS alert messages and adjust TLS settings if needed
– Issue: DNS lookup failures inside the VPN
– Verify DNS server settings inside the VPN profile
– Check for conflicts with local DNS or VPN-provided DNS
– Issue: Slow performance
– Test with and without split tunneling
– Check client logs for reconnect loops or large TLS handshakes
– Issue: MFA not prompting or failing
– Confirm MFA enrollment, time-synchronization for TOTP apps, and push notification delivery
– Issue: Platform-specific quirks
– Windows: UAC prompts or firewall blocks
– macOS: Gatekeeper and kernel extension permissions if applicable
– Mobile: background battery optimization or permission issues
– Issue: Policy mismatch messages
– Ensure the user’s policy bundle on the server matches the client version
– Confirm that the user account has the correct access permissions
– Issue: VPN tunnel not routing to internal resources
– Validate the tunnel status and route tables
– Check for misconfigured split tunneling or incorrect DNS entries
– Issue: Logging is too verbose or hard to parse
– Collect logs during a reproduction and filter by VPN events. consult IT for log analysis

Advanced topics for admins and power users

– Client-side telemetry and logging
– Use logs to diagnose intermittent disconnects or authentication failures
– Certificate lifecycle management
– Automate renewal workflows and monitor expiry dates to avoid unexpected disconnects
– Policy-aware updates
– Tie client version upgrades to backend policy updates to ensure smooth handoffs
– High-availability considerations
– For enterprise deployments, ensure multiple VPN gateways and load balancing are configured to minimize downtime
– Integrations with single sign-on SSO
– Align IdP configurations and certificate-based SSO with the F5 VPN client for seamless access
– Redundancy and failover testing
– Periodically test failover to backup gateways and verify client behavior under simulated outage

Alternatives and how F5 vpn client version compares with other options

– Cisco AnyConnect and Cisco Secure VPN
– Strengths: broad device support, mature policy features
– Considerations: integration with Cisco ecosystems, licensing costs
– Pulse Secure / Ivanti
– Strengths: strong client options, good policy control
– Considerations: vendor-specific quirks and support cycles
– OpenVPN-based clients
– Strengths: open standards, cross-platform compatibility
– Considerations: may require more manual setup for enterprise policies
– F5 Edge Client / BIG-IP APM approach
– Strengths: deep integration with the BIG-IP security policy framework, MFA support, granular access control
– Considerations: requires BIS backend alignment and enterprise licensing

When evaluating F5 vpn client version versus alternatives, focus on how well your backend policies map to the client, how MFA and certificates are managed, and what your IT team can maintain in the long run. For many organizations using BIG-IP APM, the F5 client family provides a cohesive experience aligned with their security posture.

Quick tips for users managing multiple devices

– Always verify you’re using a version that your IT policy explicitly supports
– Keep MFA available and tested on a regular basis
– Document your gateway URL and the required authentication method in a safe place
– Check enterprise VPN status dashboards or IT notices before updating
– If you’re a manager, set a staggered update window to minimize user downtime

Frequently Asked Questions

# What is the difference between F5 vpn client version and the BIG-IP APM version?
The F5 vpn client version refers to the client software you install on your device, while the BIG-IP APM version refers to the server-side appliance that enforces access policies. They must be compatible, and mismatches can cause login or connectivity issues.

# How do I know if my F5 VPN client is up to date?
Open the client, navigate to Help or About, and compare the shown version with the latest release listed in your enterprise software portal or the official F5 download site. Your IT team may also push updates automatically.

# Can I use a different VPN client with BIG-IP APM?
BIG-IP APM is designed to work with its own client ecosystem. Some environments support alternative client software, but this requires explicit policy configuration and may reduce compatibility with certain features.

# What should I do if the VPN client won’t connect after an update?
First, verify that the version is compatible with your BIG-IP APM, ensure MFA is functioning, and check certificates. If needed, rollback to a known-good version per your IT policy and retry.

# How often should I update the F5 vpn client version?
Update cadence depends on your organization’s security policy, but many enterprises aim for quarterly or semi-annual updates, with urgent patches deployed promptly for critical vulnerabilities.

# Is split tunneling safe with F5 VPN?
Split tunneling can improve performance, but it reduces the extent of traffic protected by the VPN. If your organization requires all traffic to pass through the VPN for security or policy reasons, disable split tunneling.

# How do certificates affect the F5 vpn client version?
Certificates establish trust between the client and the server. If a certificate is expired or mistrusted, the client will fail to connect. Ensure certificates are valid and trusted on the client device.

# What platforms are supported by the latest F5 vpn client version?
Windows, macOS, iOS, and Android are commonly supported, with platform-specific installers or apps. Always check the current release notes for exact platform support.

# Can I test a new F5 vpn client version without impacting users?
Yes. Use a test group or staging environment to validate compatibility with your BIG-IP APM setup before wider rollout.

# Where can I find the official compatibility matrix for F5 vpn client versions?
The compatibility matrix is typically published in the official BIG-IP APM documentation or the enterprise software portal your organization uses. Check the support portal or contact your IT administrator for access.

Useful URLs and Resources
F5 Networks Official – f5.com
BIG-IP APM Documentation – support.f5.com
F5 Community & Blogs – community.f5.com
VPN technology overview – en.wikipedia.org/wiki/Virtual_private_network
VPN market insights – statista.com/topics/1564-virtual-private-network-vpn

Turn off vpn chrome extension and disable vpn in Chrome on Windows Mac Android iOS