![]() ![]() The reason it did the scan may have something to do with my previous Windows installations and my dual, triple, quad boot configurations with Windows 7, 8, 10, 10 with different builds and so on and so forth, and different Linux distros. Windows 10 should not have even touched my J drive. I had the backup partition on a separate partition J, which is a mechanical HDD. I had Windows 8.1 installed on an SSD, system disk C, no partitioning except the RAW caching partition. I can't believe this piece of s*** for an operating system! How could it repair it? It's a 0 byte file. Thanks! I tried the KeePass repair method without any luck. Thanks in advance! I would appreciate any help I can get. I have never been so screwed by Windows! Ever! In my 20 years of using Windows! I had over 200 passwords saved in that file! only the most important file is corrupted (its data is not linked to its name or whatever). What else can I do to undo the wrongdoing of Windows 10 scan and repair process? Can it be undone? Note that it's only this file that's corrupted! All the other s**t is still intact on the partition! Conveniently. Is there any chance Recuva can recover a file whose file name is still intact but the data is missing? I mean, would Recuva even consider such file as missing? The file name itself is still there! But it's a 0 byte file! I didn't realize until now when I tried to open my KeePass file that it has become corrupted. Toward the end of the upgrade process, Windows 10 did the m*****f****** disk scan and repair b******t and I remember seeing that it scanned my J: drive. I just realized that my KeePass database has been rendered useless by the Windows 10 upgrade process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |