Let’s find what’s not working.

Start from Downloads, using your own license key. An old download link or an older copy of aimos may no longer work.

1. Open Downloads and enter the key from your purchase email. Use the buttons shown for that license: 1PC and 2PC are separate products.
2. If the page says the download is being prepared, let it finish. Avoid clicking the download button repeatedly.
3. For an update message, close the old copy and download again from the website. Use the new download with the same key. Don’t use a file sent by another customer.
4. If the download is marked unavailable or you’re asked to wait, try again later. Save the exact message if it continues.

If it still doesn’t work: Send the download message and whether it happens before or after entering your key. Don’t post the key itself.

The message matters here. A paused license, an expired license and a device change need different actions.

1. Copy the key again from your purchase email, without extra spaces. Check you opened the correct 1PC or 2PC download.
2. If the license is paused, open My account and use Resume if it is available. An admin pause or a ban needs support; downloading again will not remove it.
3. If it says expired, check the license in My account. If you bought recently and the information looks wrong, contact support with your purchase receipt privately.
4. If it says already in use, close aimos on the previous computer and wait a short time before trying again. For a changed PC or an HWID message, use the device-reset option in My account if available, or ask support.

If it still doesn’t work: Send the exact message and say whether you recently changed your PC, reinstalled Windows or switched between 1PC Color and AI.

Don’t turn off your antivirus or firewall to get past a warning. First check where the file came from and what Windows is reporting.

1. Make sure you downloaded from aimos.pro/downloads, not a message, mirror or another person’s file.
2. Read the exact warning. A browser download warning and a detection in Windows Security are not the same thing.
3. If Windows Security removed the file, open Protection history and note the detection name. Don’t add broad exclusions or restore a file you’re unsure about.
4. Send support a screenshot of the warning before continuing. Hide your key and personal details.

If it still doesn’t work: Include whether the warning appeared in your browser, when opening the file, or inside Windows Security.

Open the panel from the aimos app that is running now. A saved browser tab may belong to an earlier session.

1. Check that your chosen 1PC launcher is still running and you are signed in. Run only one 1PC version at a time.
2. Press F10 to open the current settings page. If you changed the panel shortcut, use that key instead.
3. If the browser did not open, follow the address shown by aimos. Don’t reuse an old bookmarked panel address. If a save failed, reopen the panel and check the values before applying the change again.

If it still doesn’t work: Send the exact panel message and say whether you use 1PC Color or 1PC AI. Don’t share the full local panel address publicly.

First check the selected board and USB connection. You don’t need to guess another model or repeatedly reinstall everything.

1. Extract setup.zip with Extract All, then open setup.exe from the extracted folder. Select the exact board model you have.
2. Connect only the board you’re preparing. Use a USB data cable and try a direct USB port on the PC instead of a hub.
3. For an RP board, follow Setup’s BOOT-button instructions: start disconnected, hold BOOT while connecting the PC-side port, then release it. Windows should show the board as a drive. Don’t format that drive.
4. If Setup reports a different board family, select the correct model; don’t force it. If it says access denied, close other apps using the board before retrying once.

If it still doesn’t work: Send your exact board model, a connection photo and the full error, including any S-number shown. If no drive appears, say that too.

Test normal mouse movement on the Windows desktop with aimos closed. This separates a mouse-connection problem from an in-game setting.

1. Plug the mouse directly into the PC for a quick check. If it still behaves incorrectly there, check the mouse and its cable first.
2. Reconnect it through the board using the picture for your exact model. The mouse and PC use different ports; some boards also need the correct adapter.
3. Try another USB data cable or direct PC port. If another mouse is available, test it on the same board and note whether only one mouse has the problem.
4. If the problem happens only through the board, stop there and contact support. Changing Aim settings won’t fix normal desktop movement. Don’t repeatedly run Setup or change wiring inside the board.

If it still doesn’t work: Include the mouse model, board model, wired or receiver connection and polling rate if known. Say whether the cursor pulls in one direction or moves in steps. Compatibility fixes need this detail; there isn’t one setting that fixes every mouse.

The board can appear as G203 in Windows even when your physical mouse is a different model. That name alone does not confirm the whole connection works.

1. Check normal movement and clicks on the Windows desktop with aimos closed.
2. Check that your physical mouse is connected to the mouse-side port shown for your board. Then test the mouse directly on the PC.
3. Don’t use lighting as the only test. Some mice have no lights, or keep them off. You don’t need to change lighting or use G HUB to complete the setup.

If it still doesn’t work: Send a photo of the connections and say whether the mouse works directly on the PC. Don’t add external power or modify the board without advice for that exact model.

A working mouse connection is only one part of the check. Confirm the picture, activation button and feature settings before changing several values at once.

1. Check normal mouse movement first. On 2PC, also check that your chosen video source and MAKCU are connected.
2. Enable only the feature you’re testing, save the changes and hold its assigned activation button. On 2PC, use a button on the mouse connected to MAKCU; PC1 keyboard keys do not activate it.
3. Check the target is inside that feature’s FOV. Aim, Magnet and Trigger can have different areas and activation settings.
4. For 1PC Color or 2PC, check the in-game enemy outline color matches your color settings. This color check is not a setup step for 1PC AI.
5. If Trigger or Magnet moves but does not shoot, check its activation and firing conditions in a practice area. Movement toward a target alone does not mean a shot should fire.

If it still doesn’t work: Say which feature fails, which button you hold, and whether movement, firing or both are missing. Send that feature’s settings and a short clip if possible.

First check that normal desktop movement works. Then compare one setting at a time in the same practice area.

1. Save your current configuration before changing it. Check the settings for the feature you are actually using: Aim and Magnet have their own Smooth values.
2. Lower Smooth values are faster. Increase Smooth gradually for a softer response; don’t assume the same number feels identical across different products.
3. If it consistently sits too low, check Bone Offset against the default or a saved configuration that worked. An offset changes where the aim settles; it does not repair an incorrect picture or a mouse-connection problem.
4. On 2PC, check the shared image is sharp, correctly sized and current, especially for distant targets. If the target is lost or jumps between positions, send a clip rather than compensating with extreme settings.

If it still doesn’t work: Include Aim or Magnet, Smooth X/Y, Bone Offset, FOV and whether it happens at close range, far away or both. Keep the same mouse DPI while comparing.

A page losing connection does not, by itself, tell us why aimos stopped. First check whether the app is still open on the computer running it.

1. For 2PC, check PC2. Closing the aimos window stops the app; the settings page on PC1 cannot keep it running.
2. If the app is still open, refresh the panel using the current address. If only the video stopped, check OBS or the capture card instead.
3. If the app has closed unexpectedly, note the time and what you were doing, then reopen it once. Keep any message that appears. Don’t repeatedly relaunch it if it keeps closing.
4. Tell support if it happened after changing a setting, reconnecting hardware or losing the video. If Windows error history is unavailable, you can still send these details; support can guide you through the next check.

If it still doesn’t work: Send the approximate time, 1PC or 2PC, and the last action before the problem. For 2PC, say OBS or capture card. A repeatable sequence is more useful than guessing a memory leak.

Use the same license and product when checking saved settings. A failed save or a different product can explain why the values don’t match.

1. Check you signed in with the same license and opened the same product: 1PC Color, 1PC AI or 2PC. Don’t expect their settings to be interchangeable.
2. Make one small change, click Save if the panel has a Save button, and wait for confirmation. If it shows an error, keep the page open, check the running PC has internet access, and retry after the connection returns.
3. Use Configs for your saved configurations. Read what an export code includes; a shared code may contain only some settings, not your entire setup.
4. On a different PC, check the mouse and video connections again. Restoring a configuration doesn’t connect the hardware or select a screen for you.

If it still doesn’t work: Send the save message and the specific setting that changed. Don’t post a license key or a full private configuration publicly.