WALKERBEX
HOGWARTS LEGACY / TROUBLESHOOTING

Unsupported Mod Crash? Fix Nexus Paks Conflicts.

Old loose .pak files or UE4SS hooks can break a clean launch. Check your folders, back up each file, and test without touching saves.

9 min readPC • Steam / EpicUpdated 17 Oct 2026

Hogwarts Legacy crashing with unsupported or outdated mods often means older third-party files still load with the game. The January 2025 official mod update changed compatibility for certain visual assets. This practical guide isolates legacy mod archives and common UE4SS loader files without deleting saves or uninstalling the game.

✦

Quick answer

Close the game and any mod deployment tools. Check Phoenix\Content\Paks\~mods for loose .pak/.ucas/.utoc files and Phoenix\Binaries\Win64 for UE4SS hook DLLs. Make a backup and temporarily move only the matching files, then retest. The tool below generates a local, reversible PowerShell cleanup — this webpage cannot access your PC folders.

✦
Legacy mod conflict checkerLocal diagnostic checklist + reversible cleanup script

Answer these checks before running anything. No website can inspect your files directly.

Tick any matching symptoms to see the next step.
PowerShell · preview, confirm, then move to backup
# Hogwarts Legacy legacy-mod isolation (Windows PowerShell 5.1+)
# Runs locally on YOUR PC. Backs up files rather than deleting them.
# Close Hogwarts Legacy and Vortex/other mod tools before starting.
$ErrorActionPreference = 'Stop'
$gameRoot = (Read-Host 'Paste the Hogwarts Legacy install folder').Trim('"')
if (-not (Test-Path -LiteralPath $gameRoot -PathType Container)) { throw 'Game folder not found. No files changed.' }
$paks = Join-Path $gameRoot 'Phoenix\Content\Paks'
$mods = Join-Path $paks '~mods'
$bin = Join-Path $gameRoot 'Phoenix\Binaries\Win64'
if (-not (Test-Path -LiteralPath $paks -PathType Container)) { throw 'Phoenix\Content\Paks not found. Check your install path.' }
$backup = Join-Path ([Environment]::GetFolderPath('MyDocuments')) ('HL-Legacy-Mod-Backup-' + (Get-Date -Format 'yyyyMMdd-HHmmss'))
$files = @()
if (Test-Path -LiteralPath $mods -PathType Container) {
  $files += @(Get-ChildItem -LiteralPath $mods -File -Recurse | Where-Object { $_.Extension.ToLowerInvariant() -in @('.pak','.ucas','.utoc') })
}
foreach ($name in @('dwmapi.dll','UE4SS.dll')) {
  $candidate = Join-Path $bin $name
  if (Test-Path -LiteralPath $candidate -PathType Leaf) { $files += @(Get-Item -LiteralPath $candidate) }
}
if ($files.Count -eq 0) { Write-Host 'No matching loose archives or UE4SS hook DLLs detected. Nothing to move.'; return }
Write-Host ('Files to isolate: ' + $files.Count)
$files | ForEach-Object { Write-Host (' - ' + $_.FullName) }
$ok = Read-Host 'Type BACKUP to create a backup and move these files'
if ($ok -cne 'BACKUP') { Write-Host 'Cancelled. No files changed.'; return }
New-Item -ItemType Directory -Path $backup -Force | Out-Null
foreach ($f in $files) {
  if ($f.FullName.StartsWith($mods + '\',[StringComparison]::OrdinalIgnoreCase)) {
    $relative = $f.FullName.Substring(($mods + '\').Length)
    $destination = Join-Path (Join-Path $backup 'LooseArchives') $relative
  } else {
    $destination = Join-Path (Join-Path $backup 'UE4SS-Hooks') $f.Name
  }
  $parent = Split-Path -Parent $destination
  New-Item -ItemType Directory -Path $parent -Force | Out-Null
  if (Test-Path -LiteralPath $destination) { throw ('Backup collision, stopped: ' + $destination) }
  Move-Item -LiteralPath $f.FullName -Destination $destination -ErrorAction Stop
  Write-Host ('Backed up: ' + $f.Name)
}
Write-Host ('Done. Backup: ' + $backup)
Write-Host 'Saves untouched. Launch the game. Restore only compatible mods later.'

How to run: Open Windows PowerShell, paste the script, then enter your game installation folder. Review the detected file list; type BACKUP only if the paths look correct. No administrator mode is normally necessary. It never deletes SaveGames.

The walkthrough

5 steps, in the right order.

Follow these checks one at a time, and test after each change. Start with reversible options and keep a backup.

01

Find your real installation directory

In Steam, use Library → Hogwarts Legacy → Manage → Browse local files. In Epic Games, use the installation location shown in the launcher. Confirm that the folder contains Phoenix\Content\Paks before attempting cleanup. Different PC installations use different root folders.

02

Close tools and create an independent save backup

Exit the game and any Vortex or other mod managers. Open %LOCALAPPDATA%\Hogwarts Legacy\Saved\SaveGames in Windows Explorer and copy the folder somewhere outside the game directory. This protects your character progress if you later need wider troubleshooting.

03

Run the reversible archive and UE4SS check

Copy the script above into PowerShell. It lists matching loose archives and dwmapi.dll/UE4SS.dll only from expected game locations. Confirm the paths, then type BACKUP. Nested archive directories are preserved inside a timestamped folder in Documents. Nothing is permanently deleted.

04

Start the unmodified game and verify files

Launch normally before reinstalling any unofficial mods. If it still crashes, use Steam → Properties → Installed Files → Verify integrity or Epic → Library → Manage → Verify. If a mod manager later redeploys the old files, stop and disable that profile first.

05

Reintroduce compatible mods one at a time

Official CurseForge-supported mods are installed through the in-game Play Mods interface, not through the standalone CurseForge app. Add third-party mods back only after checking their current version and required loader. If a specific mod brings the crash back, leave it out and contact its author.

✧

Important safety note

Important distinction: The script targets legacy archives and UE4SS DLLs only. It does not uninstall the official in-game mod system. Other mod loaders, injected files, or altered graphics assets may require separate manual review.

Helpful answers

Frequently asked questions

Is this the official unsupported-mod popup?

Some players see an unsupported-mod warning, while others crash during shader compilation or launch. This article addresses legacy asset/loader conflicts; exact dialog wording can vary by build.

Will the PowerShell script delete my saves?

No. It moves only specified files under the game install folder and creates a backup in Documents. SaveGames is outside the target paths. Keeping a separate save backup is still recommended.

Why can old visual mods crash after the 2025 update?

WB Games warned that engine-level changes could break certain older third-party visual and skeletal-mesh mods. Use versions declared compatible with your current game update.

Can I use Vortex and the in-game mod manager together?

They manage different types of installations. Conflicts are possible when older files remain deployed. Test with third-party deployments disabled before diagnosing the official mod manager.

What if the checker finds nothing?

Proceed with game-file verification, Windows/graphics driver checks, and a clean launch. Do not run destructive cleanup on unrelated files.

How can I undo the cleanup?

Open the timestamped backup folder in Documents and restore archived files to their original locations only after confirming they are compatible and the game is fully closed.

Double-check the facts

Official & technical references

Launcher menus, account options, and mods can change with updates. The links below help you verify the details before changing files.

End of guide · Happy exploring