Introducing AX64 Time Machine - hybrid imaging/snapshot software

UEFI with secure boot and GPT does offer more security as compared to legacy MBR. So even my 120GB SSD I use it as system drive with UEFI and secure boot. Works fine.

Also, @paulescobar I installed Windows 10 exclusively on all my old laptops (a couple of them originally came with Windows 7 and Windows , they all work fine without any driver issue. Windows 10 itself will provide almost all the hardware drivers for old laptops. The only driver I need to install manually is Realtek Audio Driver, all others were installed automatically by Windows update.
However, considering you have tight time frame to get your laptop working, I agree you'd better go with Windows 8.1 this time. Later when you have time to play around, try out Windows 10. More likely than not it will work fine without driver issue.

 

oliverjia,

Can I ask what "more security" does it offer? Against a bootkit/rootkit? Anything else? These issues can be fixed by restoring an image.

I have several UEFI systems and they are the future but I prefer MBR systems.

 

If I remember correctly, UEFI with secure boot could prevent modified boot loader from booting, therefore could potentially prevent some rootkit. Also I remember there was a ransomeware recently that will lock a disk partitioned with MBR scheme, but not the ones with UEFI/GPT.

 

To all,

When it rains, it pours.
I now have a separate issue with AX64 ( version 1.4.1.48 )

I have this spare Fujitsu Windows 7 laptop (backed up with Ax64). I replaced its hard drive tonight. Thought restoring would be a breeze...as I had the ax64 backup of the old original drive sitting on an external.

There's absolutely no problem during the restoration process:
- The Ax64 boot cd loads fine.
- I can see all drives (new internal destinaton, and external containing backup).
- Using "Open other backups", I can see the entire timeline of backups.
- During restoration, it completes 100% without error & reboots itself.

But when the laptop reboots, I get an "Operating System not found" error:
- I've checked the BIOS boot order & security settings
- I've tried restoring from different points in the timeline (all same result)
- I've tried restoring with advanced options (restore MBR, hidden partition)
- You figure there'd be some error message if the backup itself was compromised. Nothing.

Nothing works, and I can find no reason (other than God hates me) for this to occur. It's driving me insane. Because using Ax64 file explorer...I can see the restored contents of the C: drive on my new internal. It just won't load the OS.

Any ideas?

 

This old dog is still barking?

 

Paul, it sounds like you either didn't return your MBR with your restore or the restored image was not made ACTIVE when it occurred.

If you didn't do it (Advanced options), I'd restore again with the MBR checked for restoration. If that doesn't work, I'd use a Windows distribution DVD and run Startup Repair from that DVD.

The partition appears fine... it's just not been configured to BOOT from.

 

I tried both ways. Without MBR & Hidden system partition checked...and with those advanced option checked. Same result.

Some ideas I'm considering...
1) I think when you create a backup in AX64...you must manually check to backup MBR & hidden partition. Is this correct? If so, then maybe while making these backups...I forgot to check those & it is affecting the recovery?
2) Any time I examine the partitions after recovery...the "slice" is cut for what should be the "system reserved" partition, but it is completely empty and unformatted (no label either). Only the C: drive is recovered properly with content & labelling.

So it does seem like using the Windows repair function is my only resort.

 

Clearly your SRP didn't get restored properly... it is needed to BOOT from (I don't use one). I've never asked System Repair to reconstruct a SRP... pls let us know if it does it. It may just not see one (yours is unformatted), see the Windows partition, put the necessary missing BOOT files (the ones normally in the SRP) into the Windows partition and set it ACTIVE for BOOTing. That would be the best result...

 

In v1.4.1.48, I think the MBR is always checked for backup but not sure about the hidden partition (I don't don't use one... the simpler the system configuration, the better).

 

The repair has been going for at least 2 hours now. The animation runs, but no status or end in sight. So I will likely force a shut down and begin manual re-installation of software.

Thank you for your second suggestion. I am sure it will help others. But in my case, the timeline is important because I test alot of software and Photoshop plugins. So I need access to different points in timeline. Clearly, the one I had created using Ax64 on this laptop is useless. Will try again with Macrium.

This time, I will be more thorough with backups...incorporating something like full Acronis images alongside increments.
Did not in this case, because it was a temporary laptop (while actual was getting screen replaced).
But I've decided to hang on to it, and will act more responsibly as a result.

 

I have had no problems restoring using 1.4.1.48 with Win 10 and UEFI System disk.

 

FWIW, the laptop I'm referring to is purely "legacy", without any visible UEFI option.
I've also never had a problem restoring before.
But this is the first time I've done so on a new hard drive (old one was dying).

 

Did you try deleting the uefi partitions, and then making the restored C drive active?
I recall Brian guided something like that on another topic,regarding uefi to mbr stuff..

 

Before I answer you Stode, let me apologize for my previous confused post.

I just realized @silver0066's response (Windows 10 & UEFI) was in regards to my earlier query about an MSI laptop (which I'll be using soon). It's an 8.1 with UEFI. I originally showed up here asking how Ax64 would handle it.

But later, I turned up with a separate problem. My Fujitsu laptop (which I'm using currently), had a hard drive failure. And AX64 failed to restore to the new hard drive.

Now in response to you Stode...no, I did not try that. Because I test various software & plugins...I depend heavily on each snapshot. I simply lost interest in wanting to recover because I could not trust to integrity of the snapshots. So I'm just starting over and will not pursue recovering that previous Ax64 chain. But thank you so much for your interest.

 

Paul,

Your SRP didn't restore but your error message isn't right for a missing SRP. With a missing SRP and an Active Windows partition you see a BCD error. With a missing SRP and a non Active Windows partition you see a black screen. But maybe your BIOS generates a different error than mine.

To fix the missing boot files, boot a Windows disk in MBR mode
Get a Command prompt and enter

bcdboot C:\Windows /S C:

That's it. You have boot files in your Windows partition. Windows should load.
If you boot to a black screen, set the partition Active. Then Windows will load.

 

Thanks Brian. This is good general knowledge.

But I realized a few days ago, that even if I could get the OS restored...it was a pointless effort, because I really needed those particular snapshots to work properly. If I kept on with that previous backup chain, I'd have to follow your suggestion each time I reverted to one of those snapshots. Very annoying.

So instead, I'm starting over with a more proper backup process. But again, thanks for your that valuable knowledge, which I have noted for future situations.

 

To all,

This is a brand new AX64 fail on a new backup chain.
But if you think about it, you can see it explains my last issue with OS not recovering (will explain myself at end).
I think this is a serious bug in the software, but am no expert at these things.

I installed a program called "ReadyDriver Plus" on a spare Windows 7 64 Ultimate. Downloaded from this site:
http://forums.citadelindustries.net/viewtopic.php?f=14&t=4

Essentially, this software adds a boot item at computer startup. Clicking it automates entry into a Windows mode where driver checking is disabled.

To use this program, I had to make the hidden "system reserved" partition visible (gave it the drive letter "b"). The software requires access & modifies content of the "Boot" folder". Typically this is C drive. But my Windows installation put that boot folder on the hidden "System Reserved" partition. So the software made changes there.

When I was done playing with software, I decided to recover to a past snapshot ( using Ax64 1.4.1.48 ). The C: drive recovered properly ("system reserved" partition hidden again, program non-existent in Add/Remove programs).

The problem is that the software's relationship to the hidden "System Reserved" partition remains active. It still appears at computer startup as a boot item. Clicking that item still performs the automated action flawlessly.

Important to note, when I recovered I did check "Restore hidden system partition" & "Restore MBR". Shouldn't that have completely removed the program? Why would the boot item remain?

------------

EDIT #1: IMO, there seems to be a relationship between my last recovery issue. Ax64 is failing to recover the hidden system partition.

In my previous issue, the OS would not boot up. I observed that it would restore what should have been the system reserved partition...as unallocated space. This caused my OS not to boot up because in my setup...the "Boot" folder is located on that hidden partition.

In this issue, what I think is happening is that instead of restoring the hidden partition as unallocated...it simply leaves it alone. This is causing that software's boot item & functionality to linger over any restores.

--------------

EDIT #2: I just performed a test to confirm Ax64 is not backing up or restoring the hidden system reserved partition.

I placed custom named text files at various locations of the partition. I then restored to past snapshots. The text files are still there & untouched.

Is it just me? Or is this a major flaw in the program?

---------------

EDIT #3: After performing more research on this thread, I think I have stumbled on a cause.

In this past post, ISSO states that ".axb" files represent backups of the hidden system reserved partition.
https://www.wilderssecurity.com/thre...snapshot-software.339999/page-47#post-2223382

Well, in my backup folder, I have absolutely no ".axb" files. I only have ".axd" files. No wonder Ax64 is not recovering my SRP...it simply has no backup!

I am considering a possible cause. I use a custom backup location & name. The path & name are very long ( "K\Database\Backups\-- Ax64 Time Machine -- " ).

Maybe this has been screwing up the backup process? I will now perform a test, starting a new backup chain with default location...and see how it deals with SRP.

 

Paul, pls remember... you are dealing with an old version of AX64. I'm not sure all this valiant effort on your part is worth it. Even if you identify a flaw, nothing will ever be done with that version as far as the Devs are concerned.

Even this morning, on Bits Du Jour, a 4-pak of AX64 Time Machine (not FlashBack) is being offered for $19.95... that's very old software being offered at bargain basement prices. Seems like a barrel scrape to me...

 

...and as I mentioned before, AX64 v1.4.1.48 works fairly well with the simplest of configurations... that being NO UEFI and NO SRP. There were problems "back in the day" associated with UEFI and with LEGACY that incl. SRPs... we don't even know if they were completely cleaned up when they moved to v2 of Time Machine (before the FlashBack days).

My (and many other's) success with v1.4.1.48 was almost always predicated on a Legacy-MBR system that only incl. the BOOTable Windows C: partition, nothing else. This is easy to CLEAN INSTALL to if you pre-partition your disk first with at least 1-partiton, then install Windows to that partition or the one you want if you pre-partitioned more than one. This creates a BOOTable Windows partition with no SRP... a very simple configuration.

 

Yes. It is a hopeless cause.

Especially now that I have conducted my little test.

FWIW, even with default save location setting...same problem persists.
SRP is not backed up at all, under any circumstances.
Restoring it absolutely does not work.

Mr. Frog, are there any similar problems regarding SRP with Macrium?

 

Paul,

Dont know if its helpful but...

I am running AX64 V2 on Win 10 64. C & E partition here. I protected C with AX64 & backup on E partition with default backup folder name. Here the backup folder has .axd & .axb files for every backup created.
I have tried quite a few hot & warm restore & no probs.
Legacy BIOS here.

If I remember correctly...I tried Android on PC & it creates boot option...after restore with AX64 Android boot option was not there.
If I will try Android on PC again then will confirm here.

 

None whatsoever. Your choice of backups are... 1)The partitions YOU want to backup (your choice, all available), or 2)What's needed to BOOT your system (Macrium backs up whatever's needed, partition-wise, to successfully BOOT your system, regardless of BiOS BOOTing type <Legacy-MBR or UEFI>). If you create your DEFINITION during this process (optional), it remembers everything needed to do any additional imaging (Incrementals <snapshots>, Differentials or Fulls) using that DEFINITION.

 

So, in UEFI system, is it not wise to install FlashBack?

 

FWIW, I purchased this offer and the serial provided WILL register FlashBack build 703, which I think is the latest release. I used it on a trial version I had already installed. Hopefully it will remain registered whenever the next version is released...

 

What was said is it was not wise to install AX64 Time Machine v1 on an UEFI machine. FlashBack at Build 703 is a much improved beast in the area of more extended (UEFI, etc.) system builds.