Introducing AX64 Time Machine - hybrid imaging/snapshot software

I made them both in 8.1

 

Thanks David,

Yes, AX64 still has problems with making Recovery Media on Windows 8.1. I believe the problem lies with WinRE.wim.

The WinRE.wim for either Windows 8 or 7 will not work with Windows 8.1. I have tried this and it gives BSOD.

Maybe, Isso or Denis can step in here and give some guidance. Maybe, if they can upload a good WinRE.wim on their site and give some directions how to copy it to C:\Recovery\WindowsRE.

David, in the meantime, if you want me to upload WinRE.wim, I can do this and also post the copying directions too.

Best regards,

Mohamed

 

Hi David,

Here is the link for downloading for WinRE.wim:

https://dl.dropboxusercontent.com/u/3762325/winre.wim

Posted in the following link, InstallTakeOwnership.txt which is registry entries for "TakingOwnership". Wilders' doesn't allow to upload .reg files, so change the InstallTakeOwnership.txt to InstallTakeOwnership.reg and import it into registry for allowing to "TakeOwnership":

https://www.wilderssecurity.com/showpost.php?p=2319313

Then Windows Explorer show everything so that you can see C:\Recovery. Take Ownership and go inside and you will see a sub-directory WindowsRE. In it you will find WinRE.wim, change to WinREOld.wim and then copy my WinRE.wim.

Anywhere in C:\Recovery if you find WinRE.wim, change it to WinREOld.wim.

If it might not allow you in the regular Windows, then go Safe Mode and you can do it there.

Best regards,

Mohamed

 

I know the EasyBCD instructions for AX64 have been posted many times here by Mohamed and I have used the search but it just leads me to this thread which now is like 255 pages and I scrolled thru but can't find the BCD instructions. It would take me hours to go thru all these pages so can someone give me the page it is on or a link? This time I will copy the instructions into an email to myself for future reference.Thanks.

 

Hi Uffbros,

With the new version of AX64, you can install it through the program itself. But if you need the instructions for EasyBCD then I will post it again.

In AX64, go to create "Recovery Media" and you will find "Local Storage" to install AX64 as boot menu.

Best regards,

Mohamed

 

Dear Uffbros,

On the following page are the instruction for EasyBCD for Macrium Reflect. The instructions remain the same for any imaging program, including AX64:

https://www.wilderssecurity.com/showthread.php?p=2316958#post2316958

Best regards,

Mohamed

 

Hi Mohamed

Thanks for doing that.

I have d/l the Winre, Reg file and made C:\Recovery visible but it will not allow me to access the folder. Under the folder properties I have allowed all but still will not allow me access.

Is there a way round this please?

Just noticed you mentioned Safe Mode so will try that.

 

Hi David,

Sorry, for not fully posting the instructions. Right click on C:\Recovery and you will find "Take Ownership" in the right click menu. So you need to take ownership before it will allow you in the directory. Hopefully, you have installed the registry file.

Best regards,

Mohamed

 

SanyaIV, I noticed no one has completely answered your question so I'll give it a try.

Anytime, any partition access occurs for the protected partition from OUTSIDE of the running Windows OS (incl. entry into the new local storage recovery feature of AX64), the next time AX64 runs from inside of the protected Windows OS, you will get the message "External volume modification detected." This occurs when running a LINUX recovery CD of any kind that opens the protected partition for any reason (just looking, for example), as well as any other BOOTable process that may access that partition (WinPE, WinRE, BartPE, etc.). Even if the BOOTable process is just opening that partition for examination, that will occur.

The reason... AX64 TM, while under the protected Windows OS, keeps an active tracking file, incl. last access date/time, of the Windows file structure. It must do this to be able to determine what the differences are between where it is and a selected snapshot for RESTORE purposes. It can only be sure of these differences if nothing external has changed its protected partition. If there has been changes, it's knowledge of the current file structure has been compromised and it must go back and remap that structure. That's what's taking the long snapshot period following an external partition access. As you noticed, once it's done that, only the normal incremental snap size is generated. Until the next external access is created, that remapping of the structure is no longer required so all following snaps are very quick, as expected.

It's just a product of the application's design.

PS- Happy New Year to ALL!

 

Hi Mohamed

Just discovered it was being blocked by Voodooshield so the reg file did not run. Solved that so that the option is now listed, however I still cannot gain access to the folder.

I can't get safe mode on this machine. I think that F8 will bring up the option but that is also my BIOS boot menu. Anyway I used the file explorer on my Active@ USB stick and renamed and copied the Winre file as you suggested.

Went back into Windows and re made the local folder and USB stick but still get the same result with both boot options - just end up with a black screen and working mouse pointer.

This is not a bother for me as I have the alternative method but am happy to try help debug the program.

 

Factual, precise & very helpful...as ever.

Wishing you a Peaceful & Prosperous New Year too, Frogster!

 

I run 8.1 and my right click menu doesn't have take ownership

 

Hi Uffbros,

You need to install the registry entries for "InstallTakeOwnership".

See the following threads:

https://www.wilderssecurity.com/showpost.php?p=2321887

and

https://www.wilderssecurity.com/showpost.php?p=2319313

Best regards,

Mohamed

 

I mean make an image , but not restore an image on WinRE/WinPE.

I could not make an image on WinRE which is based on Win7 x86.

 

Hi Andylau,

You mean making a COLD Image instead of HOT Image. No AX64 doesn't and will never do due to it unique technology, which one needs to understand. AX64 is two programs into one:

1. Imaging program.
2. Snapshots program.

The snapshots should only be restored within Windows. No another imaging program has achieved this feat. In those rare case when a snapshot fails to restore, then one needs to go into WinRE and perform the restore. In this case it will perform a full restore, rather than the restore of just that snapshot.

AX64 team is working on those rare instances, when HOT snapshot restore fails, the failure rate is about 20%. So, there should never be a need to go into WinRE. This will add about 10 seconds to the HOT snapshot restore, which is very, very fast, and those 10 seconds don't matter. What matters is 100% reliability.

Every time, one enters WinRE it messes up AX64 thinking. And, the next snapshot however, how small takes a long very, very time. WHY?

Froggie, has explained this nicely in the following post, read it very carefully and you will understand AX64 fully:

https://www.wilderssecurity.com/showpost.php?p=2321919

Best regards,

Mohamed

 

AX64 is two products into one:

1. Imaging program like Image for Windows or Macrium Reflect.
2. Snapshot program like Rollback Rx.


What is AX64 Time Machine and how it works:

http://ax64.uservoice.com/knowledgebase/articles/202490-what-is-ax64-time-machine-and-how-it-works


Disk Imaging vs Snapshotting:

http://ax64.uservoice.com/knowledgebase/articles/202415-disk-imaging-vs-snapshotting


Best regards,

Mohamed

 

aladdin,

You know my question now. Making an image on WinPE/RE must be cold image.

I know these before. When AX64 is released I have asked this question, but at that time, the developer said AX64 could not make an image on WinPE/WinRE.

I just asked again to see whether it could do that or not now.

Honestly, imaging is more important and useful than snapshot for me. I like doing cold image because no extra background services are running.

 

Thanks for the detailed response.

 

Hi Andylau,

Thanks for fully explaining. I understand now!

Best regards,

Mohamed

 

@Isso

I am trialling the latest beta 1.4.0.19 - as opposed to 1.2.1120 it works on my machine (Win 7 x64) - the previous version would screw up the file system with both hot and cold restores (had sent a ticket about this).

5 hot restores have worked without issue. Recovery media has created and booted flawlessly.

There is one remaining issue for me, and that is the error message in the event log after each restore: The previous system shutdown was unexpected. It is particularly meaningful as I am running a RAID 1 (mirror set) of two HDs containing my data files. After each restore, I get this message and the RAID 1 needs to resynch - a major pain in the butt.

Have sent a support ticket.

 

Hi newbino

Good to hear latest beta works for you. In regards to the event viewer notification, this is common due to how the application restores work. In my experience, all images taken from within windows or what is called "hot image", upon restore will cause the event viewer to note improper shutdown, or unexpected shutdown in the case of AXTM "hot restore", after its restore, it performs an immediate reboot, so as not to allow any disk writes after a hot restore and this is considered by windows as NOT a normal shutdown procedure, so windows will note this as unexpected after an AXTM hot restore, and likely it will note an improper shutdown even restoring via boot media.

The reason AXTM or most other imagers that one can create a hot image from within windows causes this event report is because in reality, there is no record there was a proper shutdown sequence, due to a hot image (created from within windows), so upon a cold restore, I have found most imaging apps after an image restore will cause an event viewer notification stating as such, no record of proper shutdown or unexpected shut down. It is the nature of hot imaging or in the case of AXTM, even hot restores, because of how AXTM has to shut down the system quickly and reboot. This is not a proper shutdown, but it is also not considered a problem nor has it caused me any issues other than telling you there actually was NOT a proper shutdown, or there was an unexpected shutdown, this is true, it is just the nature of most hot imaging apps. I do not experience this when I create images outside of windows, or "cold imaging" with IFL or Macrium or Aomei, etc. Now if I used Macrium, or Aomei, etc., to create an image from within windows, upon restoring this image, there will be in this case the improper shutdown notification because of no record of a shutdown after the image was created "hot". I believe it has to do with what is called 'dirty bit' not being reset after a hot image was taken or something to that effect. But this is not an issue when restoring an image created "cold" or outside of windows.

Isso has commented on this before and explained why AXTM must operate this way, and in my experience, any hot image restore or a restore of an image that was created inside windows will always report a shut down issue. Otherwise, it does not affect the quality of restore.

Now you should not have experienced any file system corruption, so glad to hear the latest beta solved this. File system corruption after a restore can usually be corrected via windows check disk (chkdsk) utility, but it is not a good thing to have this happen. I have found this to be the case with some quick restore type apps.

A proper sector based restore should never cause file system problems unless there is a restore problem with the application. I had this problem testing out Toolwiz Time machine and stopped using it due to this. Some have not had this issue or at least have not checked the event viewer after a restore, but it happens in some cases.

Hope this helps in some way

have a good day!

Jim

 

so does usb/local restore of v.19 is working with win8.1?

don't want try the test again since my last restore screwed my system (and i have to reinstall win8 then update to Win8.1

 

Serious System Failure: Question re: AX64

Guys, I've been in the process of slowly migrating from my old XP system to my Win 7 system as I felt the XP system was on its last legs. Was waiting to bring the data over after I had all my programs set up to my liking.

And then, , I booted up the XP system this morning, and after the XP screen (black), the screen just goes dead/black, like there's nothing connecting to it. (Monitor is okay, works with the Win 7 system.) Many reboots, cold boots, no difference.

AX64 is on the Win 7, but not on this XP system as I am still using FD-ISR until I abandon this computer. Attempts to choose a prior FD-ISR snapshot, even a year back, results in the identical system behavior. That says to my limited tech expertise, that this is a hardware problem.

By the way, I was able to boot up in Safe Mode and am almost done transferring the 400 GB of data to the new computer.

1. Your thoughts on this being a hardware issue, and suggestions?
2. If I had installed AX64 is this type of situation, might it have been effective, where FD-ISR was not?
3. The only thing I know I did last night, was to remove the USB cables for my two printers to connect them and install drivers on the new computer. Do you think THAT could be causing such a conflict?

Very grateful for any input. Functioning in Safe Mode, while essential right now, is making my eyes hurt!

 

I am using V1.4.0.18 with good results. However I see comments about V1.4.0.19 but can't find where to download it to try. Can someone point me to it? Thanks in advance.