Pes 2013 Registry File 64 Bit May 2026

To add a key/value: Right-click → New → select type (String, DWORD, Binary).

To remove: Right-click → Delete.

For programmatic changes, use PowerShell (e.g., Get-ItemProperty / Set-ItemProperty) or reg.exe.

Example PowerShell to read an install path (assumes Wow6432Node):

Get-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\KONAMI\Pro Evolution Soccer 2013"

Example PowerShell to set fullscreen:

Set-ItemProperty -Path "HKCU:\Software\KONAMI\Pro Evolution Soccer 2013" -Name "Fullscreen" -Value 1 -Type DWord

When editing 32-bit keys from a 64-bit PowerShell/Regedit, ensure the process accesses the correct view; PowerShell supports -RegistryView parameter (Registry64 vs Registry32) in .NET registry APIs.

If you own the Steam version of PES 2013 (delisted in 2018 but still downloadable for owners), Steam manages the Registry automatically. Do not manually edit the Registry for Steam games unless you have moved the installation folder using Steam's "Move Install Folder" feature.

Here is the core issue: On a 32-bit Windows system, the Registry path for PES 2013 looks like this: Pes 2013 Registry File 64 Bit

HKEY_LOCAL_MACHINE\SOFTWARE\KONAMI\PES2013 To add a key/value: Right-click → New →

On a 64-bit Windows system, however, Microsoft introduced a compatibility layer called WOW64 (Windows 32-bit on Windows 64-bit). This layer redirects 32-bit application registry calls to a separate branch: When editing 32-bit keys from a 64-bit PowerShell/Regedit,

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\KONAMI\PES2013

When you double-click a standard .reg file scraped from a 2006 forum, it often writes to the wrong path (the 32-bit branch). The game, running under WOW64, looks in the WOW6432Node—and finds nothing. This is why you need a dedicated "64-bit registry file."