Why should you not boot from another O.S. (external media) on a system with Safecode Defencecure installed?

One of the Safecode Defencecure product limitations is Booting From an External Media (OS) – Safecode Defencecure cannot protect the computer when changes are made to the hard drive from an external or foreign (non-Windows) operating system bypassing Safecode Defencecure system drivers. For example, booting from a Windows PE CD will start a different OS that may change the hard drive and produce unpredictable results.

We frequently get asked by users why they cannot boot from a PE CD after installing Safecode Defencecure?

Let’s take a closer look at this limitation with an example:

  1. You have a barebones Windows 10 system.
  2. You install Safecode Defencecure on the system. The setup creates the Baseline snapshot.
  3. You then install MS Office on the system and create a snapshot Office. The Office snapshot contains Windows 10 and Office.
  4. You then restore the system to the Baseline snapshot and install Adobe on the system and create a snapshot Adobe. The Adobe snapshot contains Windows 10 and Adobe.
  5. Now, if you restore the system to the Baseline snapshot, you only see Windows 10.
  6. If you restore the system to the Office snapshot, you will see Windows 10 and Office.
  7. If you restore the system to the Adobe snapshot, you will see Windows 10 and Adobe.

All these are obvious and easy to understand, it’s what you expect from Safecode Defencecure.

You also need to understand when you are in the Adobe snapshot, even though you do not see the office files, the files must exist on the hard drive. Because when you restore the system to the Office snapshot, you will see the office files.

You don’t see the office files while in the Adobe snapshot because those files are not “registered” in the Windows file system. The files only exist in Safecode Defencecure snapshots.

Each Safecode Defencecure snapshot is What You See is What You Get (WYSIWYG) at the time of creating the snapshot, and of course, each snapshot could have different files.

You can see the office files while you are in the Office snapshot because Safecode Defencecure drivers can load the files from the snapshot.

Now the question is, if you boot up the system with a bootable Windows 7 PE CD (you are essentially booting a Windows 7 O.S.) and look at the system, what files should you see?

Do you see Windows 10 files (files from the Baseline Snapshot) or office files (files from the Office snapshot), or Adobe files (file from the Adobe snapshot)?

The answer is that you will NOT see any files added to the system after installing Safecode Defencecure because those files exist in Safecode Defencecure snapshots. We need to load Safecode Defencecure drivers to read the files from snapshots.

When you booted from the Windows 7 PE CD, the system did not boot from the Windows 10 O.S., and therefore Safecode Defencecure drivers did not load.

Now you have the picture. When you are in the Windows 7 PE environment, you do not see the files in Safecode Defencecure snapshots, but those files DO exist on the hard disk. If you write some information to the disk from the PE environment (even if you do not write anything to the disk, the PE system might write cache or temp files on the disk), there is a chance you could write over the sectors used by the Office and Adobe files contained in the Office and Adobe snapshot and therefore damaging the snapshots!
 

This is why you should not boot from another O.S. (such as the Windows 7 PE disc) on a system with Safecode Defencecure snapshots.

Powered by BetterDocs

Leave a Reply

Your email address will not be published.Required fields are marked *