| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 147989 | 2019-06-09 11:32:00 | System Restore fails twice. | kioti (17360) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1461392 | 2019-06-09 22:26:00 | Hmmmmm..... well I guess that a System Restore isn't going to work if the System has been cleaned and taken back to a time before the crap happened and all the craps been removed. | kioti (17360) | ||
| 1461393 | 2019-06-10 00:34:00 | doh! :groan: | bevy121 (117) | ||
| 1461394 | 2019-06-10 01:16:00 | Hmmmmm..... well I guess that a System Restore isn't going to work if the System has been cleaned and taken back to a time before the crap happened and all the craps been removed. Figuring out when it was infected is the trick. |
piroska (17583) | ||
| 1461395 | 2019-06-10 01:45:00 | Figuring out when it was infected is the trick. piroska_ hi. I knew when it was infected, as soon as I installed the update driver for the MS USB Keyboard I have. That came after I installed Driver Max so the restore point I chose first was the one shown in the pic that Shows Driver Max instal. Going back to before that time would have been fine. But I had cleaned all the crap from the computer the day it happened, so I do not know why Restore wouldn't go back to before Driver Max instal or the Windows Update the day before that. .So it was after the fails to restore that I used an Aomei Disk backup I created on 25th May after I upgraded from v1809 to v1903 direct from Windows Data Creation tool option instead of Downloading an .iso to burn to disc or a bootable usb drive. Now it remains to be seen how long its going to take me to corrupt this nice clean W10 v1903 Pro x64 I am using. :D cheers ps: I had the same problems with restores when I was using Eset Nod 32 about 8 years ago when I used W7x64 Pro..... try to do a restore and couldn't because Nod 32 had locked away files from earlier! hahahaha |
kioti (17360) | ||
| 1 2 | |||||