Internal Error 123 and no Boot

[WilliamP]

I am having a problem. When I create a snapshot I get errors. It has had a pop up saying Internal Error 123. How can I determine what is causing the error? When I View log it just shows that there was errors. How do I dig deeper?

[stapp]

When you view the log have you clicked on the blue plus sign?

Takes great patience to scroll and find the errors.

Is this a first snapshot of a newly installed First Defence?

[WilliamP]

I have tried several snapshots.

[WilliamP]

Thank you for the help. I was clicking on the wrong thing. I have problems [DCF Backup write access denied],Replacing [Windows\system32\drivers\cmdmon.sys ]and Replacing Windows\system32\ drivers\inspect .sys. Both drivers are Comodo Firewall but I don't have a clue to DCF.

[WilliamP]

I did some further searching and went into Comodo and told it to not protect itself. FDISR works like a champ now. I do love that program.:thumb: ;D

[Longboard]

It's often an issue with any apps that have 'termination protection' enabled
Typically security type apps.
In a strange way it's nice to see that those utilities are doing their job, but creates irritation for snapshot creation and copy/update.

Disable the tools giving a problem for new snap creation and copy/update then re enable protection while working in that or other snaps.

Raxco support has been back on line recently: :) : set up a support ticket; they may be able to create a newer copy engine with the developers as these issues arise with various utilities.

Similar issues with PG ( strong termination protection as we know)and CyberHawk.

Btw: was there ever a version of Fdisr copy engine that did eventually work with PG??

There was this older thread re PG
http://www.wilderssecurity.com/archive/index.php/t-141069.html