To avoid losing data, one should create a temporary full disk image before running any sort of disk checking / file system ''“repair”'' tools. But `AUTOCHK.EXE`, a Windows program in the folders *System32* and *SysWOW64*, might decide to call `CHKDSK.EXE` (Windows equivalent for Linux's `fsck`) on boot when it decides that it is necessary. ## My experience Side note: I mainly use Linux Mint. But when I once booted Windows after having used a live bootable Linux, and I left the computer, Windows decided to launch `AUTOCHK.EXE`. When I came back, I saw that hundreds of files and folders have been moved into `C:\found.000` and have been renamed into `file00000000.chk`, `file00000001.chk`, …, `file00000009.chk` and `file0000000A.chk`, `dir_00000001.chk`, etc… . Some of those files were saved HTML pages. Because they were renamed, their HTML files were disconnected from their respective resource folders (e.g. file:`sitename1.html`, folder:`sitename1_files`). ## Disarming AUTOCHK Rename `AUTOCHK.EXE` to anything else, such as `AUTOCHK.EXE.bak`. You may also delete it entirely, but I would recommend just renaming it.