Documents vanished yet remained on the storage after verification
Documents vanished yet remained on the storage after verification
Hello, upon restarting my PC recently, it performed a disk check before launching. Initially, I ignored it until I logged in and noticed that most of my Steam titles were listed as uninstalled, preventing any Xbox Gamepass games from loading. It seemed like all the Steam files on my D: drive vanished completely. There was no Steam directory in Program Files, and even when I manually searched for the address, nothing appeared. I suspect the same problem is impacting my Gamepass games too, since they were saved to the same drive. However, I’m not sure if the files were actually deleted because my remaining space on D: remained unchanged, suggesting they might still exist. I’ve tried searching online for solutions but haven’t found any answers. I’ve enabled hidden folders to verify this isn’t an issue. If anyone could explain what’s happening or suggest a fix, that would be greatly appreciated. I’ve restarted several times without success, and my C: drive files appear unaffected, with the games there functioning normally. I’m using Windows 10 64-bit ROG STRIX B360-H, Intel i9-9900k processor, 32GB RAM. Any additional details about these components might help. Thank you in advance for your assistance.
I refer to the process of organizing and removing unnecessary files from your system. It wasn't just a simple scan; it provided detailed output showing what was cleaned.
It seems like this might have been a disk check process a few days back. I don’t remember any output from it, just that it scanned all my files before opening the login screen. I’m sorry for the lack of clarity, but I’m not very experienced with this and thought fixing it would be simple, though I don’t have any tools at hand.
If ChkDsk was used, a log file should exist. To access it: 1. Open the Start menu. 2. Enter "Event Viewer" in the search bar. The Application window opens. 3. Choose Windows Logs (second option on the left side). -> Application (first sub-option). 4. Find event ID 1001 with a source of "Winnit" or "Winlogon" and the correct ChkDsk run date, then select it. 5. Check the "General" tab in the lower section to see the details.
I handled the matter and found the log. The details below are the spoilers. I’m not completely sure of all the meanings, but your help is appreciated. Thanks so far! For clarification, please let me know. Spoiler Checking:
- File system type: NTFS
- Volume label: Storage
- One disk needs checking for consistency.
- You can skip the disk check, but it’s recommended.
Windows will now inspect the disks.
Stage 1: Examining basic file system structure...
- Deleted corrupt attribute list entry with type code 80 in file 109.
- Unable to find child frs 0x18f with sequence number 0x2.
- Deleted another corrupt attribute list entry with type code 80 in file 109.
- No child frs 0x18d with sequence number 0x2 found.
- Attributes with same type code 0x80 but different instance tags have non-contiguous VCN numbers.
- One attribute of type 0x80 and instance tag 0x0 has an incorrect allocated length.
- Expected size is 66c1f000, but actual is wrong.
- Corrected total allocated size in file record (80, "") for segment 5000000000109.
- Deleted another corrupt attribute list entry with type code 80 in file 109.
- Couldn’t locate attribute with instance tag 0x0 and segment reference 0xa0000000000f1.
- Expected type is 0x80.
- Deleted corrupt attribute record from file record segment 0xF1.
- Unable to find attribute with instance tag 0x0 and segment reference 0x9000000000115.
- Expected type 0x80.
- Deleted corrupt attribute record from segment 0x115.
- Unable to locate attribute with instance tag 0x0 and segment reference 0x500000000011f.
- Expected type 0x80.
- Continuing deletion process...
File verification completed.
Phase duration: 41.07 seconds.
Orphan file record segments processed: 562,944.
File verification successful.
Please confirm if this matches your expectations.
Disk Check typically activates when there’s a problem with the Windows file system or a hard drive. If it ran recently and now fails, it’s likely due to an issue with the drive itself. I often notice this when a drive is deteriorating—it can trigger Disk Check automatically. Consider running a smart diagnostic on the D: drive using tools like HD Tune or Crystal Disk Info to assess its condition. Based on its age, especially for mechanical HDDs, it may be wearing out over time.
Downloaded Crystal Disk Info reports your HDD is functioning well. After nearly two years, it’s unclear if that’s considered outdated, yet the tool doesn’t detect any issues. Here are the findings: Spoiler – a solution might exist. If storage capacity had grown with this upgrade, you’d likely have accepted the loss; now you’re facing a challenge. I’m unlikely to support a complete HDD reset. Besides, is there another option to recover lost files or erase them completely?