Set of scripts to detect and repair system corruption for Windows. (eg. disk fail, file system errors, etc.)
-
Clone the repository to some folder, or just downloads and extract it.
-
It's usually advised to start with
Checkup.bat; Right-click on it and select Run as Admin. -
Paste this in an admin PowerShell:
cd '~\Documents\Scripts\Corruption Toolbox\' # Change to repo directory $VerbosePreference = 'Continue' & .\filediff.ps1 -Verbose 4>&1 | Tee ~\Desktop\diff.log & .\filerestorer_smart.ps1 & .\Heuristic_corruption_finder.ps1 -Verbose 4>&1 | Tee ~\Desktop\heu.log
If you don't want the extra verbose outputs, or the console logs, simply run them like this:
cd '~\Documents\Scripts\Corruption Toolbox\' # Change to repo directory & .\filediff.ps1 & .\filerestorer_smart.ps1 & .\Heuristic_corruption_finder.ps1
-
Run this in the directory that
to_bash_script.txt(created from previous step, desktop by default). Before that, theto_bash_script.txtshould be edited to have its address style mathching your bash engine (e.g./c/or/mnt/c/), encoded in UTF-8 with LF line endings.cd ~/Desktop bash bash_deeper_heuristic.sh
Assuming
bashis an alias for msys2, mingw, or wsl ... (everything running bash in windows), with windows admin access (that is different from sudo in the linux-side). You may need to set executable usingchmod +xdepending on your platform. -
Run
regread.ps1as admin. You can run this anytime because it doesn't depend on previous steps. -
You can run the
Reset...batch files if you have issues in those areas. (Run as admin as always).
-
You should have a bash interpreter on windows to run deeper heuristics (and some utility bash scripts). This can be ideally MSYS2/MinGW (they are also available in git-bash) or cygwin. You can also use WSL2 with cross OS file access, but most tools used in this repo assume windows awareness to some degree (preferably compiled for windows). The path schemes used in this repo use MSYS2 or git-bash style.
-
You should have 7z and rar/unrar CLI executables installed on your system and added to
PATHso they are available in powershell and your bash interpreter. (look at item 1)