Bloodborne on PC—a PS4 game that, for years, many of us never thought we would get to play this way. Thanks to a community-made Windows project, exploring Yharnam on a PC is now possible.
This guide covers downloading the Windows launcher, extracting compatible game files, applying the matching update, and launching the game.
This is an unofficial community project. It is not affiliated with Sony Interactive Entertainment or FromSoftware, and the launcher does not include Bloodborne’s game files. The project requires your own compatible, decrypted game dump. Its documentation identifies CUSA03173 and specifies version 1.09 for its community patches.
Copyright and educational-use notice: This article is for educational purposes only. GetDroidTips does not provide copyrighted game files or links to unauthorized downloads. In the United States, 17 U.S.C. § 106 protects copyright owners’ exclusive rights, including reproduction and distribution, subject to statutory limitations. The DMCA’s 17 U.S.C. § 1201 generally prohibits circumventing access controls, subject to applicable exceptions and exemptions. Owning a copy does not automatically authorize every method of obtaining or decrypting game files, and an educational disclaimer does not make an otherwise unlawful activity legal. Follow the laws applicable in your jurisdiction.
Download the Bloodborne Windows project from GitHub
Find the Windows build you want to use and read its release notes. Expand Assets, then download the packaged Windows ZIP.
Select the actual Windows release package rather than either of GitHub’s automatically generated Source code archives.
After the download finishes:
- Right-click the ZIP file.
- Select Extract All.
- Open the extracted folder.
- Locate the
bbport-windows folder used in this setup.
- Move it to a permanent location, such as a dedicated Games folder.
Keep all files supplied with the launcher together. Moving only the executable can leave required components behind.
Step 2: Check Your Available Storage
Before extracting the game, make sure the destination drive has enough free space.
During installation, you may have several copies of the same data: the original packages, extracted base-game files, extracted update files, and the completed game folder. Leave additional space for temporary files and copying operations.
Keep the original packages until you have confirmed that the completed installation launches successfully. This makes it easier to repeat an extraction if something goes wrong.
Open the extractor’s release page:
Download ShadPS4Plus PKG Extractor 1.1
Download the Windows archive and extract it into a separate folder.
Use version 1.1 rather than 1.0. The developer states that version 1.1 fixes a problem that could corrupt files when extracting packages larger than 2 GB. The tool also supports dragging a PKG file onto its Windows executable; without a separate output path, it extracts beside the package.
For convenience, keep the extractor and launcher within one main setup directory, but in separate subfolders.
Step 4: Verify the Base Game and Update
This walkthrough uses the following combination:
| Component |
Version used in this guide |
| Bloodborne base game |
CUSA03173 |
| Bloodborne update |
Version 1.09, matching CUSA03173 |
| Separate DLC |
Optional, compatible with the selected game and build |
Check the complete title ID on both your base game and update before continuing.
Do not assume that an update for another title ID will work simply because it is also labelled Bloodborne. Renaming a folder does not change the identity or compatibility of the files inside it.
Your packages must already be in a form supported by the extractor and Windows project. This guide starts with compatible, decrypted files and does not cover obtaining or decrypting them.
Open the folder containing the PKG Extractor executable.
- Locate your compatible Bloodborne base-game PKG.
- Drag it onto the extractor executable.
- Allow the extraction to finish completely.
- Check the resulting game folder.
Extraction time depends on the package size and your computer’s storage performance. Avoid closing the extractor or moving the package while it is working.
Before continuing, confirm that extraction finished without an error. An incomplete folder may still contain some recognizable game files but fail when you try to launch it.
Repeat the process with the matching update package:
- Locate the version 1.09 update for CUSA03173.
- Drag the update PKG onto the extractor executable.
- Wait for extraction to finish.
- Identify the extracted update folder.
Keep the base-game and update contents distinguishable until you are ready to merge them. If your extractor’s output naming would cause them to overlap, place the source packages in separate working folders before extraction.
If your setup includes a separate compatible DLC package, extract that as well. Otherwise, skip the separate DLC step.
Step 7: Apply the Update to the Base Game
Once both packages are extracted, copy the update files into the base-game folder.
- Open the extracted version 1.09 update folder.
- Select the contents inside it.
- Copy those contents.
- Open the main CUSA03173 base-game folder.
- Paste the update contents directly into that folder.
- If Windows asks how to handle duplicate filenames, choose Replace the files in the destination.
- Wait until the copy operation finishes.
Copy the update folder’s contents—not the entire update folder—into the base-game folder.
The updated files must occupy the corresponding locations in the main game directory. Leaving them inside an extra nested update folder will not accomplish that.
If Windows reports a copy failure, resolve it before proceeding. A partially applied update can leave you with a mixture of old and new files.
Step 8: Add Optional DLC Where Supported
Skip this step if you are not using a separate DLC package.
The accompanying tutorial uses a package layout with an inner content folder copied into the main game directory. Treat that as specific to the demonstrated package structure.
Before copying anything, check the DLC instructions for your chosen build. If your extracted package looks different, do not guess which folder belongs where. Follow the project’s documented layout for that package.
Step 9: Move the Completed Game Folder
After applying the update and any supported DLC, move the completed CUSA03173 folder to its permanent location.
You can keep it alongside the launcher folder within your main Bloodborne installation directory. Keep the game’s internal files and folders intact.
Locate eboot.bin in the completed game folder. You will use the folder containing that file when configuring the launcher.
Avoid moving the game again after setting its path unless you also plan to update the launcher’s configuration.
Step 10: Select the Game Folder in the Launcher
Open bbport-windows and double-click Bloodborne.exe.
For the launcher layout shown in the tutorial:
- Open Game and Effects.
- Find Game Folder Path.
- Click Browse.
- Select the completed CUSA03173 folder.
- Confirm your selection.
Choose the actual game folder containing eboot.bin. Selecting the parent directory, extractor folder, or update-only folder can prevent the launcher from finding the game.
Some releases may display a first-time setup wizard instead. If yours does, select the same completed game folder when prompted and complete the required checks.
Leave the remaining options at their defaults for the first launch. Once the game works, you can adjust settings individually and compare the results.
Step 11: Launch Bloodborne and Test Gameplay
Connect your controller, then click Play.
Allow time for the game to start. Once you reach gameplay, test more than whether the opening screen loads.
Spend a few minutes checking:
- Character movement and camera control.
- Dodging, attacking, and targeting enemies.
- Lighting and visual effects.
- Audio during exploration and combat.
- Performance when entering another area.
A successful launch is a useful first check, but it does not guarantee that every area will behave the same way. Performance and stability depend on your hardware, project build, settings, and game files.
If you change settings afterward, adjust one option at a time. That makes it easier to identify which change improves performance or introduces a problem.
Troubleshooting Common Setup Problems
The following checks can help narrow down an installation issue. They are starting points, rather than guaranteed fixes.
The launcher cannot find the game
Check that the selected folder contains eboot.bin.
Also confirm that you selected the completed base-game directory and that it has not been moved since you configured the path.
Confirm that you are using PKG Extractor 1.1 and that the destination drive has sufficient free space.
Read the extractor’s error message before trying again. Repeat extraction into a clean working folder if the previous attempt was incomplete.
The game fails to start after applying the update
Recheck the base-game and update title IDs.
Then confirm that you copied the update’s contents directly into the base-game folder and allowed Windows to replace matching files. If the copy was interrupted, rebuild the completed folder from your original packages.
The launcher opens, but the game crashes
Record the exact error message and consult the release notes for your installed build.
If you changed settings or added modifications, return to the initial configuration and test again. Change one variable at a time so you can identify what affects the crash.
Gameplay is slow or visually incorrect
Start with the build’s default settings and review its documented hardware requirements and known issues.
Use the launcher’s supported graphics options to test a less demanding configuration. Avoid applying several patches or settings changes simultaneously, as this makes troubleshooting harder.
DLC does not appear
Check compatibility and the folder instructions for your particular build and package. A folder name alone is not enough to determine whether the content has been installed correctly.
What to Include When Asking for Help
If you need assistance, include:
- Your processor, graphics card, and RAM.
- Your Windows version.
- The exact Bloodborne project release.
- Your game’s title ID and update version.
- The complete error message.
- Whether the problem occurs during extraction, launch, loading, or gameplay.
- Any settings or modifications you changed.
You can leave those details in the GetDroidTips comments along with the step where the issue occurred. Clear information makes it much easier to identify whether the problem comes from the file preparation, launcher configuration, or gameplay itself.
