I spent an evening getting a community-built native PC port of The Last of Us Remastered running on Windows 11, and almost all of the friction came from desktop hygiene rather than the game: an unverified download, a missing runtime, and an antivirus that quietly removed the executable.
Here is the order I would follow again. Set aside 30–45 minutes plus download time. You need 64-bit Windows 10 or 11 with admin rights, 7-Zip, the Microsoft Visual C++ Redistributable 2015–2022 (x64), a current NVIDIA/AMD/Intel GPU driver, and the port's release archive next to its published SHA-256 checksum.
One caveat up front: these ports are unofficial hobbyist builds shipped from their own release pages, so there is no download URL in this article. Each release carries its own file names, version numbers and minimum specs, and those notes are the only authority. Everything in angle brackets — <port-executable>, <port-release-archive> — is a placeholder you replace with the exact name from the notes. If a release page publishes no checksum, treat that as a red flag.
Before you start: the checklist
Confirm the basics first, because each of these turns into a confusing error later:
- 64-bit Windows 10/11 — run
winverand you should see something like Windows 11, Version 23H2 (OS Build 22631.xxxx). Anything below Win10 64-bit is a hard stop. - A local administrator session, since installing runtimes and adding Defender exclusions both need elevation.
- 7-Zip, because release archives are usually
.7zand Explorer cannot open them. - VC++ 2015–2022 x64 — the shared library package most compiled Windows games link against. Without it the executable simply refuses to start.
- The latest Game Ready / Adrenalin / Arc driver.
- Free space equal to the release-notes figure, plus roughly 2 GB of extraction overhead.
- The archive and its checksum value.
Step 1: Verify the archive and snapshot your hardware
A SHA-256 hash is a fingerprint of a file: change one byte and the fingerprint changes. Truncated downloads and stale drivers cause most of the "black window flashes and closes" reports, and hashing costs seconds while re-downloading costs an hour.
Get-FileHash -Algorithm SHA256 "$env:USERPROFILE\Downloads\<port-release-archive>.7z" You want an Algorithm column reading SHA256, a 64-character Hash, and the expected Path. Compare that hash to the published value character for character.
Then record which machine you are on, so you can rule hardware out later:
Get-CimInstance Win32_VideoController | Select-Object Name, DriverVersion, DriverDate Get-PSDrive C | Select-Object @{n='FreeGB';e={[math]::Round($_.Free/1GB,1)}} Example output: NVIDIA GeForce RTX 3060, a DriverVersion starting 5xx.xx, and FreeGB 84.3. If free space is below the release-notes figure, move the archive to another drive before going further.
Step 2: Extract to a short path and prepare the environment
Three things bite here. Long paths containing spaces or non-Latin characters break builds whose internal asset loaders concatenate paths without quoting. The executable is unsigned, so Defender may quarantine it mid-extraction. And you will want a log from the very first launch.
& "C:\Program Files\7-Zip\7z.exe" x "$env:USERPROFILE\Downloads\<port-release-archive>.7z" -o"C:\Games\TLoUR" -y Get-ChildItem "C:\Games\TLoUR" | Select-Object Mode, Length, Name A healthy listing shows the executable plus at least one data folder:
Mode Length Name ---- ------ ---- d----- data -a---- 73400320 <port-executable>.exe -a---- 1024 README.txt If Defender removed the executable, add the exclusion and re-extract — but only for a folder whose hash you verified in Step 1:
Add-MpPreference -ExclusionPath "C:\Games\TLoUR" Step 3: Launch through a batch file so failures are visible
Double-clicking the .exe throws away stdout, and a port that dies on startup usually prints the reason exactly there. Create C:\Games\TLoUR\launch.cmd in Notepad (set the file type to All Files):
@echo off cd /d C:\Games\TLoUR "<port-executable>.exe" > launch.log 2>&1 Run it and read the tail of the log:
& "C:\Games\TLoUR\launch.cmd" Get-Content "C:\Games\TLoUR\launch.log" -Tail 20 On a good first run you will see renderer-initialisation and window-creation lines, and the game window appears within a few seconds.
Step 4: Prove it is native, then tune graphics
"Native" means the executable was compiled for x86-64 Windows and talks straight to DirectX or Vulkan — no emulator imitating console hardware in software. Check for emulator processes, then check that the port itself is running:
Get-Process | Where-Object { $_.Name -match 'rpcs3|yuzu|ryujinx|cemu|shadps4' } | Select-Object Name, Id Get-Process -Name "<port-executable>" | Select-Object Name, Id, Path The first command returning nothing is the proof: no emulator is loaded. The second should return one row pointing at C:\Games\TLoUR\<port-executable>.exe. Now open Task Manager → Performance → GPU and confirm the 3D engine graph follows the in-game load instead of sitting at 0% — that is how you catch the port rendering on the wrong adapter.
Only after that, open the in-game graphics menu and set the resolution to your monitor's native value. If the build ships an .ini or .cfg, edit it with notepad and change only keys that already exist in that file. Unknown keys are either ignored or break the parser, depending on the build.
Troubleshooting: two errors you will probably hit
Missing DLL. The code execution cannot proceed because VCRUNTIME140_1.dll was not found. The VC++ 2015–2022 x64 runtime is absent, so the executable cannot resolve its C++ standard-library dependency. Install vc_redist.x64.exe from Microsoft, reboot, rerun launch.cmd, and verify with Get-ChildItem C:\Windows\System32\vcruntime140_1.dll — the file must exist.
Instant exit with 0xc000007b. The application was unable to start correctly (0xc000007b). This points at a 32-bit/64-bit mismatch somewhere in the chain, so re-check that the redistributable you installed is the x64 build and that nothing 32-bit is being pulled in alongside the port.
Takeaway
The port itself was the easy part. What decided whether the evening worked was verifying the hash before trusting the archive, extracting into a short ASCII path, having the x64 runtime already in place, adding a Defender exclusion deliberately rather than out of panic, and capturing stdout from the first launch. Do those five things in that order and most failures become a readable log line instead of a mystery.
This article was originally published on AI Release — https://ai-release.org, and more guides like it show up in the channel at https://t.me/ai_release1.



