YOUR FIRST GAME
Set up S2Arm on Windows for iPhone or iPad
Seven steps from the official Windows launcher to your first playable scene on iPhone or iPad, with checks and troubleshooting at each stage.
You confirm each step yourself. We cannot detect your device or game. Skipping does not count as completion.
Steps and saved status
- Step 1: Download and fully extract Not marked
- Step 2: Prepare the build environment Not marked
- Step 3: Import your keys and first game Not marked
- Step 4: Choose the target and build Not marked
- Step 5: Connect and prepare signing Not marked
- Step 6: Install the app and import resources Not marked
- Step 7: Reach a playable scene Not marked
Use the official Windows x64 launcher to build on your PC, then install over a cable. Complete the device and materials check first. Button names below describe the action; wording can vary with the launcher language.
STEP 1 OF 7
Step 1: Download and fully extract
Open the official v0.2.8 release. Download S2Arm-windows-x64.zip, not “Source code”. This route follows v0.2.8; if you choose a later version, read its release notes for changed requirements.
Extract the entire archive in File Explorer, then open S2Arm.exe from the extracted folder. Keep the adjacent Engine, Runtime and other folders. Do not run inside the ZIP or move only the executable to your desktop.
Use a normal local folder for the launcher, away from folders continuously managed by download software. Put the working game library on a suitable local NTFS/ReFS drive with space available. Check the drive's Properties if unsure. Avoid a cloud sync folder or exFAT external working library for your first run.
Success check: The launcher opens and shows the computer, keys and game preparation flow.
STEP 2 OF 7
Step 2: Prepare the build environment
Resolve missing items in the computer preparation / environment check. The official package includes most runtime components; do not start by installing an entire Python or .NET development environment.
If Windows Metal tools are missing, follow the check's official link, sign in with your own Apple account, and install Metal Developer Tools for Windows. Return and run the check again. If already installed but not detected, use the manual installation-folder option and select its actual directory. Launcher source
If bundled components are missing, download and fully extract the official package again. If a game's shaders currently require a Mac, this is a support limitation: follow the error guidance or use a Mac route. Repeating installation will not add support.
Phone connection and signing can wait until the installation stage. Passing the environment check before selecting a game does not guarantee enough disk space.
Success check: The checks needed to build pass, with no missing item blocking preparation.
STEP 3 OF 7
Step 3: Import your keys and first game
- Select your complete
prod.keysin the keys step for ordinary NSP/XCI input. - Choose Add Game and select the base file or the folder containing its base, updates and DLC.
- Wait for reading to finish. Open result details if only some items succeeded, and address the failed items rather than repeating everything.
- Check the game name, version and missing-content notices in the library.
Success check: The correct game appears, keys are usable, and no required base content remains missing.
If the launcher was extracted into the default library folder, v0.2.8 chooses an unused folder for the library instead. If library setup still fails, read the reason and use Try again or Choose another folder. An old immediate “another task” message at first Add Game may have been this setup failure; do not wait for a task that never started.
Upgrading from v0.2.7 and seeing garbled game names? v0.2.8 repairs affected Windows indexes on the first library open. See game and keys import errors for the distinction from a failed game import.
STEP 4 OF 7
Step 4: Choose the target and build
Select the game, open the build action and choose iPhone / iPad. Confirm the requested target information and output location, then start. The welcome flow may offer a one-click build action.
Keep the PC powered and awake. Extraction, program translation, shaders and packaging take different amounts of time. Someone else's build duration is not a deadline for yours.
Watch the task stage, completed amount and error messages. A running timer alone does not show useful progress. Record the stalled stage and message before deciding what to do.
Success check: The build finishes without an unresolved failure. A yellow warning such as zero precompiled shaders needs the update and rebuild guide.
The game is not on your phone yet. You do not need to upload the IPA to another website.
STEP 5 OF 7
Step 5: Connect and prepare signing
- Connect the target device with a data cable and unlock it. Trust the computer only after confirming it is yours.
- Open the installation action for this game and check the selected device.
- Resolve the installation checks. If Apple device support is missing, install a supported version of Apple Devices, or use iTunes where supported by the launcher's checks.
- If the check specifically requires official iCloud, use Apple's download guidance, then check again. This is a signing dependency, not a request to sync your games to iCloud.
- The official Windows package includes Impactor. Follow the launcher's flow to sign in and verify your own Apple account there, then return to the installation check. Missing Impactor suggests an incomplete package; obtain the full package first.
- If requested, enable Developer Mode under Settings → Privacy & Security on the device, restart and confirm after restarting. If the switch is absent, complete pairing through the installation flow first. Apple guidance
Success check: The selected device is the one actually connected, and account / device checks allow installation. A model dropdown alone is not device detection.
If Windows reports Apple ID sign-in expired / Apple error 1100, use Open Impactor to sign in again, renew the same account's sign-in there, then retry installation. Rebuilding will not renew the login. See the 1100 recovery steps.
See device detection or Apple error 9401 if blocked.
STEP 6 OF 7
Step 6: Install the app and import resources
Start installation. Keep the cable connected and the device unlocked. Signing, app installation and game-resource transfer are different stages. Do not disconnect just because the S2Arm icon appears.
If the computer says resources have transferred and one final step remains, open S2Arm on the phone, select the game and keep the app in the foreground until import finishes. That message does not require transferring everything again. Related upstream issue
Success check: Transfer has finished on the PC, and the target game on the phone no longer reports missing resources or a pending import.
An empty library, 0 KB progress or a resource error? Use empty library and resource transfer to identify the stage. v0.2.8 also fixes a Windows first-install failure when S2Arm is already on the phone but contains no games and the installer says it cannot read installed games. Update and retry normal installation for that specific case; it is different from resources still waiting to import.
STEP 7 OF 7
Step 7: Reach a playable scene
Select the game in S2Arm on your phone and launch it. Reach a scene you can interact with, then try movement or menu input. A library card or opening video alone does not confirm playability.
For a black screen or crash, note whether it happened at the intro, loading a save or entering a scene. Keep the software and game versions and use the problem report outline. Do not randomly change keys or signing accounts.
v0.2.8 fixes some OpenGL launch crashes caused by missing graphics functions. Check the update guidance if you are coming from an older version; it is not a fix for every game or crash.
Success check: You can actually control the game. Continue to save backups, signing renewal and your next game.
Sources: v0.2.8 release, versioned interface text, official package error handling.