AnyPS5 on Windows: download to relink.

Requirements and caveats

Use a Windows x86-64 host, correctly matched AnyPS5 libraries, an appropriate Vulkan 1.1 graphics device/driver, and a clean ELF executable with its bundled modules. The upstream project may not implement APIs required by your title. Windows' total memory commit limit can also block titles allocating large direct-memory regions.

1. Download both official components

On the download page select relinker-v0.1.1.exe and prx-windows-v0.1.1.zip. Both link straight to the original GitHub release. Do not mix Windows with Linux PRX archives.

2. Prepare the source directory

Place your legally obtained clean ELF next to a sce_module/ or sce_modules/ directory (or prx/ according to upstream rules). Example:

workspace/
  relinker-v0.1.1.exe
  source/
    input.elf
    sce_module/
      <bundled ELF modules>

The upstream Relinker errors when both sce_module/ and sce_modules/ are present, or when none of its accepted module directories exist. This site does not provide any executable or original PS5 modules.

3. Generate a Windows executable

Open PowerShell in the workspace and run:

.\relinker-v0.1.1.exe --windows source\input.elf app.exe

For an Intel host, add --to-intel if needed to translate supported AMD-specific instructions:

.\relinker-v0.1.1.exe --windows --to-intel source\input.elf app.exe

Do not omit --windows. Naming the file app.exe does not change the default Linux ELF output format. Unsupported input instructions can still fail conversion.

4. Complete the runtime directory

Extract the Windows PRX library archive and place the host-built system *.prx files under libs/. Keep the converted title's modules under app0/ as printed by the Relinker. Add your separately authorized application assets in app0/:

workspace/
  app.exe
  libs/
    <AnyPS5 host system libraries>.prx
  app0/
    <app resources>
    sce_module/
      <converted title modules>

Windows builds may also require libgcc_s_seh-1.dll, libstdc++-6.dll, and libwinpthread-1.dll from the matching MinGW toolchain near the generated executable or on the library path. The upstream technical-debt file identifies this requirement. Then try:

.\app.exe

Common Windows failure patterns