first time install error.
Got the same one tonight
this shit is annoying does anyone not know a fix or whats causing this?? i checked the dir its saying the file is in and i have a patch.fat but no patch1.fat wtf??
See https://github.com/rootCBR/DisruptManager/issues/23#issuecomment-2585329454.
Verify that you set everything up correctly. If that doesn't help, there might be a bug.
I've released an update that should fix the problem.
https://github.com/rootCBR/DisruptManager/releases
Let me know if it works.
root can you plz fix this patch.1.fat issue.
the update didn't work for me at all. the patch1.fat file is still missing.
does anyone have a fix or an alternative to disrupt
Doesnt work, same issue.
Give the new update a try and see if it's fixed
Still not working : Not saving the path of WDL No folder "data_win64" so no file "patch1.fat"
https://github.com/rootCBR/DisruptManager/issues/10#issuecomment-3411504156
this should help @grimdour @SilentWorkForce @rootCBR @JoshFanti @Pepper134 @YeraTV @Neon-Reaper @froomfie @leo13578 @byronvaz47
You’re trying to install mods for Watch Dogs Legion, but the game directory was configured under the wrong profile (e.g., the Watch Dogs profile instead of the Watch Dogs Legion profile).
Because of that, DisruptManager ends up using the wrong file expectations for the selected folder and throws:
FileNotFoundException: ...\data_win64\patch1.fat
This is misleading, because Watch Dogs Legion normally uses:
-
patch.fat/patch.dat - plus language packs like
patch_brazilian.*,patch_english.*, etc.
While patch1.fat/dat is typical of Watch Dogs 2 (and may also appear in older/other profile logic). So the folder is usually fine — the issue is that the folder is being handled by the wrong game profile.
Fix (user-side)
- Open Profiles.
- Click/select “Watch Dogs Legion” (not Watch Dogs / Watch Dogs 2).
- Set the Game Directory for Legion there.
- Also make sure the Watch Dogs Legion checkbox is enabled, so it appears in the dropdown list while DisruptManager is open.
- Retry the install.
Suggestion (developer-side)
It would help a lot if the tool could warn the user when the selected directory doesn’t match the active profile, instead of failing later with a missing-file exception (which looks like a broken install). This would prevent a very common user mistake and reduce confusion/support requests.
i was installing them for watch dogs 2 not watch dogs legion but i did get them to work
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Anderson Assunção @.> Sent: Saturday, December 13, 2025 7:54:08 AM To: rootCBR/DisruptManager @.> Cc: tarnishedXsoul @.>; Comment @.> Subject: Re: [rootCBR/DisruptManager] first time install error. (Issue #24)
[https://avatars.githubusercontent.com/u/116029665?s=20&v=4]A-Assuncao left a comment (rootCBR/DisruptManager#24)https://github.com/rootCBR/DisruptManager/issues/24#issuecomment-3648267313
2025-12-1217-35-12-ezgif.com-crop.gif (view on web)https://github.com/user-attachments/assets/dea42db4-8bc8-4516-b20d-f29317d0d035
You’re trying to install mods for Watch Dogs Legion, but the game directory was configured under the wrong profile (e.g., the Watch Dogs profile instead of the Watch Dogs Legion profile).
Because of that, DisruptManager ends up using the wrong file expectations for the selected folder and throws:
FileNotFoundException: ...\data_win64\patch1.fat
This is misleading, because Watch Dogs Legion normally uses:
- patch.fat / patch.dat
- plus language packs like patch_brazilian., patch_english., etc.
While patch1.fat/dat is typical of Watch Dogs 2 (and may also appear in older/other profile logic). So the folder is usually fine — the issue is that the folder is being handled by the wrong game profile.
Fix (user-side)
- Open Profiles.
- Click/select “Watch Dogs Legion” (not Watch Dogs / Watch Dogs 2).
- Set the Game Directory for Legion there.
- Also make sure the Watch Dogs Legion checkbox is enabled, so it appears in the dropdown list while DisruptManager is open.
- Retry the install.
Suggestion (developer-side)
It would help a lot if the tool could warn the user when the selected directory doesn’t match the active profile, instead of failing later with a missing-file exception (which looks like a broken install). This would prevent a very common user mistake and reduce confusion/support requests.
— Reply to this email directly, view it on GitHubhttps://github.com/rootCBR/DisruptManager/issues/24#issuecomment-3648267313, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHYSUL6LMGQSF5HJT4ODYXL4BM2QBAVCNFSM6AAAAABUB3J7QGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBYGI3DOMZRGM. You are receiving this because you commented.Message ID: @.***>