System Requirements
Current AskCc desktop platforms, installers, devices, permissions, and network requirements.
Which operating systems does AskCc support?
| Platform | Current support |
|---|---|
| macOS | macOS 13 or later, with Apple silicon and Intel installers. M-series is recommended; use macOS 26 or later when possible. |
| Windows | Windows 11, or fully updated Windows 10 22H2. The public installer is x64 only. Some Huawei PCs are currently incompatible; Huawei users should complete a full self-test of core features before using AskCc in a real interview. |
Linux, Windows on ARM, browser, and mobile clients are not currently available.
Which installer should I download?
On Mac, choose Apple silicon for an M-series chip or Intel for an Intel processor. On Windows, choose the x64 installer. If you are unsure, open About This Mac and check Chip or Processor.
Use the download page for the latest installer and current platform notes.
What devices and network access are required?
- A working microphone;
- The system output used by the meeting app;
- A stable, low-latency internet connection;
- Enough memory and disk space to run AskCc and the meeting app together;
- Permission to use the microphone, screen capture, and system audio on macOS;
- Clear, readable screen content for screen questions.
AskCc’s real-time features require the network and do not work offline.
What should I know about multiple displays or remote desktops?
Test screenshots, overlay placement, and content protection on the exact display and meeting app you will use. Remote desktops, virtual machines, enterprise security software, and unusual capture tools can change permission, audio-routing, and window-capture behavior; not every combination is supported.
How can I verify compatibility?
Run this minimum check:
- Install and sign in to AskCc.
- Confirm that the intended input and output devices appear in Audio & Permissions.
- Confirm that both audio tests show activity.
- Create a test profile with a language, resume, and JD.
- Start a short session and verify transcripts, answers, the screenshot shortcut, and overlay behavior.
If a step fails, send the operating-system version, installer architecture, device names, and failed step to Support.