---
description: >-
  One of the most critical steps is to ensure that the PPU hash of the patches
  matches with the hash of P5.
---

# Finding P5EX's patch's PPU-hash

## Finding the PPU hash

Go to your P5EX\_PRX\_PATCH > patches.

![Contents of the patches folder.](https://675170313-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkPt8lyxo8yTecTbFdF%2F-MkdKgDd78gKfy6swOaX%2F-MkdN4wFrguP3XtSSBoE%2Fimage.png?alt=media\&token=38947492-b261-4127-a16a-6ecc24264c8d)

Inside is a file titled: “patch.yml”, open it in the text editor of your choice. In my case, I used VSCode.

If this is your first time seeing this, don’t worry. W**hat’s important is finding the PPU hash** that’s found in this file.

Navigate to Edit > Find, this will open the find window. (Shortcut is **Ctrl + F on Windows**). Now search for: **PPU**

![](https://lh5.googleusercontent.com/5BeAeLjiem9n-uq0HyGTgFrTjsRVuERNDjDQ945r2PqsnEPcZEdMM6jlcr8zaRNUlYY6AfAFV5q9Ge5nbjX7HcRrPA27DwhT1C7HLEk6i8to7q48ste2b0up637A_zifBkEf5WMh=s0)

**There should be two hits in the search results.**

{% hint style="danger" %}
**Please keep your patch.yml open as this is necessary for the next few steps in the guide.**
{% endhint %}

## Where to next?

We need to find P5's PPU hash so that we can compare it with P5EX's patch's PPU hash, which thankfully is the next page of this guide.

_If you know how to find the PPU hash of P5 you can jump directly to Comparing hashes:_

{% content-ref url="../comparing-hashes" %}
[comparing-hashes](../comparing-hashes)
{% endcontent-ref %}
