It didn’t move anything. The filesystem got corrupted and that directory was erroneously marked as unused space, which is probably why you were running chkdsk in the first place. Lost and found is the correct place to put files recovered this way because chkdsk doesn’t know where they’re supposed to go. Fsck does the same thing and in fact lost+found is a default directory on most (all?) unices
It failed to fix itself. Yes, I “ignored” it for a few days as I had no time to sit for it to check the drive - when I was ignoring the prompt it was still working. It would have broken itself earlier, and I would have been even more screwed. And no policies for backup were allowed by IT, other than a couple files on OneDrive.
It didn’t move anything. The filesystem got corrupted and that directory was erroneously marked as unused space, which is probably why you were running chkdsk in the first place. Lost and found is the correct place to put files recovered this way because chkdsk doesn’t know where they’re supposed to go. Fsck does the same thing and in fact lost+found is a default directory on most (all?) unices
Windows was able to boot for a week, prompting me every time, until I didn’t manage to skip it one day. Then it bricked itself
So it tried to warn you that the filesystem was fucky and you ignored it
It failed to fix itself. Yes, I “ignored” it for a few days as I had no time to sit for it to check the drive - when I was ignoring the prompt it was still working. It would have broken itself earlier, and I would have been even more screwed. And no policies for backup were allowed by IT, other than a couple files on OneDrive.