Know your game files

CUSA03173: Bloodborne PC Port Compatibility Guide

CUSA03173 identifies the European Game of the Year edition of Bloodborne. It is a title ID, not the 1.09 update number, a PC launcher or a download format.

Read the guide

Before you begin

CUSA03173 alone does not prove that your files match a project’s requirements. Check the game revision, executable and selected runtime together. The original bbport documents other retail title IDs too; compatibility is project-specific.

Chapter I

CUSA03173 and 1.09 mean different things

Think of CUSA03173 as the edition identifier and 1.09 as a software revision. A folder named CUSA03173 can still contain an older executable, incomplete files or the wrong update. Renaming a directory changes none of those contents.

The original bbport validation code reads metadata from sce_sys/param.sfo and examines the executable’s loaded image. This matters when a displayed version and the actual eboot.bin disagree. A folder label or metadata string by itself is not a reliable acceptance test.

Three separate identifiers to record
FieldExampleWhat it tells you
Title IDCUSA03173Which retail edition the files identify
Game revision01.09 / 1.09Which game update is present
Runtime releaseA project-specific tagWhich community program you are running

Chapter II

CUSA03173 support depends on the project

Read this as documentation evidence, not a gameplay certification. CUSA03173 is explicitly named in several setup instructions, but that does not make it the only supported edition everywhere.

Documented game-file requirements by project
ProjectDocumentation evidencePractical implication
Original Linux bbportNames CUSA03173 and other retail IDs with the 1.09 executableCheck the executable, not only the edition
Supermedo WindowsIdentifies CUSA03173 as GOTY; discusses base-game DLC separatelyUse its current game-folder validation
Mrsuss60 Windows loaderSpecifies decrypted CUSA03173 files and eboot.bin 1.09Follow this loader’s narrower documented requirement
bbhostRequests updated game data and a particular decrypted 1.09 ELFCUSA03173 folder naming alone is insufficient

Chapter III

Check your CUSA03173 folder

Locate the game root that actually contains eboot.bin. Avoid selecting an outer archive directory or a nested CUSA03173 folder that contains only another folder. Keep your original dump and saves backed up before applying your own matching update.

If CUSA03173 data needs update 1.09, follow that runtime’s documented update layout. Some workflows merge an update over the base game; another may support a separate update directory. Do not mix those layouts without checking the maintainer’s instructions.

  • Confirm CUSA03173 is the title ID in the actual metadata, not just a folder name.
  • Confirm the game data and executable belong to the intended update.
  • Run the selected project’s normal validation before adding patches.
  • Record the exact message if validation refuses the files.

Chapter IV

Diagnose a CUSA03173 mismatch

An eboot.bin not found message usually calls for checking the selected path and extracted folder structure first. A CUSA03173 version mismatch is different: the program found files but cannot accept their revision or contents.

The original bbport checker distinguishes an old update, metadata/executable mismatch, unreadable executable and a known prepatched 60 FPS image. Restore compatible clean files from your own copy and matching update. Do not edit the metadata or bypass validation to hide the problem.

A CUSA03173 checksum is meaningful only with its documented method. bbport’s loaded-image fingerprint and a whole-file SHA-256 are different calculations; comparing them directly can produce a false mismatch.

Questions, answered

Frequently asked questions

Does CUSA03173 include The Old Hunters?

Supermedo’s documentation identifies this as the GOTY edition with the expansion. That does not prove a particular dump is complete, nor that another edition’s DLC setup is identical.

Can I rename CUSA00900 to CUSA03173?

Renaming cannot convert an edition or update its executable. Use the real title ID and the selected project’s supported game checks. The original bbport explicitly documents other retail editions.

Where is the CUSA03173 download?

This guide explains identification and compatibility; it does not distribute game files. The download guide links community program releases, which require your own compatible game copy separately.

Will a CUSA03173 mod work with every runtime?

Not necessarily. Match the mod’s game revision, loader and patch format as well as its title ID. Start from a clean working installation and test one change at a time.

Follow the evidence

Sources & verification

These primary sources support the project-specific details above. Maintainer documentation can change; check your release before applying instructions.

How this site checks its sources