Welcome in our world.
I ended with a Windows image six month older. Fortunately I didn’t loose anything important.
Maybe you’ll have luck with a developer to guide you. :-TU
OK,
CTM corrupted your MBR. There is no fixing anything and Comodo knows that.
Your problem is well documented and has happened to MANY. Including me.
All you can do is reformat and reinstall your OS. You already lost everything.
Sorry. Comodo knows about it and lied that the last patch fixed it.
For Comodo to ask you to patch after your MTR was corrupt explains how little they know about what they do. They should know that’s impossible.
Since when can a damaged MBR not be repaired? What do you think that a reformat does? It will fill the MBR to default boot sequence code. Guess what, some of the repair tools can do that too, and your system will boot again (without CTM boot console).
I don’t think my MBR got 100% ■■■■■■■… The system is able to Boot but Windows fails to load some important files…
Also the CTM Sub-Console got lost during the process so no pressing HOME at startup.
Currently scanning the drive to find all files it can detect, and it seems like I can recover most of them.
The MBR is not my biggest issue, that does not contain real data.
You need to be certain in this case to NOT WRITE ANY data to the affected disk, and use a boot CD or the drive as a Slave in an other system (careful OS could write unwanted data to disk). With every write you make to the affected disk you create the risk to overwrite sectors that contain “lost data”.
Current setup is:
First I created a complete RAW Image from the affected disk (40GB) to an External USB drive using DriveImageXML.
So in case i ■■■■■ up with the recovery i can restore the Image and are back to problem day 1.
Next:
Hiren’s Boot CD, with an External USB disk attached to the system, booted “Mini XP” and now trying to find what tool can find the most data back.
It looks like CTM manipulates multiple copies of the NTFS table structure ($MFT) to represent a current state to the Windows OS, I found multiple $MFT entries who could be related to the number of snapshots that where on the system.
Switching between detections of these shows indeed some differences, based on a single file i knew i just downloaded before i chose to select “reset baseline”.
And scans based on file modification date’s.
Really, Name one instance where a corrupted MBR was successfully repaired WITH CTM installed? There are none. There have been claims in these forms but all were borked.
We have reproduced this issue and will fix it as soon as possible. And my suggestion is when you encounter problems which cause system cannot boot, please contact to us instead of reinstalling or reformatting. We will try our best to help you to restore your system.
Well, I had a corrupted MBR and I contacted your support. After you offering several generic suggestions that didn’t work, you stopped contacting me leaving me with a computer that wouldn’t boot. My only solution because of this, was to reformat and reinstall the OS.
I would recommend that you leave communication on this issue to the public forum so others can be helped.
The instructions are for downloading a WinPE iso with the Snapshot scavenger program to try to mount snapshots so you can recover your data.
I have no idea if this Rollback RX program will work with CTM snapshots, but thought I mention it in case
someone else runs into this problem and wants to try it to see if it works with CTM.