Introducing AX64 Time Machine - hybrid imaging/snapshot software

I went to 1133 because it is the version SUMo reports as latest!

 

Hello Mohamed....how?

 

I use a tool called EasyBCD to make the AX64 boot ISO available on boot time. Easy and very convenient.

 

OK...thanks
Any other way. Not wanting to spend 30 bucks for the option.

 

It's freeware for private use.

 

Opps..I will take another look. Clicked on first hit. Often a bad idea.

 

First hit I got on Google is fine. Says on their page that it's free for personal use.

http://neosmart.net/EasyBCD/

 

It's not the latest stable version, SUMo doesn't always flag betas right away.

 

The latest unofficial is 1145:

http://www.ax64.com/other/

 

Is this pretty good on win7 64 bit?

 

I have it on W7 64bit and W8 64 bit.

 

Thank-you
Edit: installed the 1145 but shows as 1.2.0.1131 isn't that weird

 

If you go in the backup browser and check the About box, it says build 1145.

 

found that, thank you again

 

Tyreman, I tried to respond to your PM but received an error that stated:

"Tyreman only accepts private messages from members on Buddy List"

Acadia

 

Opps I removed the check mark on that box
Should be okay now.

 

If you browse back thru the previous posts in this thread,
you will find two tutorials on how to do it.
One by Mohamed, one by me.

Here's the link to mine, the pictures should be quite easy to understand:
http://imgur.com/0BYjEVo,3yS6yX9,IMJHsgM#0

edit:
You will need (well the tutorials atleast use it..) EasyBCD which is freeware and can be obtained here

 

I'm losing confidence in AX 1120. Restores from the browser on x64 W7 SP1, although in the correct pre-snapshot state, end in a "frozen" desktop. Neither the USB keyboard or mouse function. I just force shutdown, restart and choose "Start Normally" and the restore is successful. Why do I have to do it that way? I'm reasonably sure this all started after all the issues with the last Windows updates everyone was experiencing. Thank you!

 

Well, if your issue is caused by the Windows updates, then it's not V1120's fault. I'm sure if Isso had continued with the upcoming version that would have been addressed. As soon as Isso comes back next week with the news of AX64's future, I'm sure developement will start again under the new what ever.

 

You may or may not have noticed that Isso has been mostly absent from the thread for the last 3 or 4 weeks. He has indicated that something is up with AX64 and that he will be able to return (HOPEFULLY < my thought) next week and explain whats going on. It sounds like AX64 bug fixing is proceeding while this situation is being resolved and the freezing issue is the main bug being dealt with. Hopefully Isso is able to return next week and let us know whats going on and hopefully a new release will be forthcoming shortly thereafter.

Do you get a sense that I am hopeful?

PS edit: there is a beta update if you want to try it. Some have found it helpful and others not so much. I assume its still available on the AX64 site but if not perhaps someone who has a copy can send it to you to try.

 

Thank you for the reply! I have been keeping up here only to the point that I knew Isso was mostly missing. I actually posted because I knew you regulars seem to know as much about the app as anyone. Anyway, I did not realize this (freezing issue) has been happening frequently as is sounds like it has from your response. Normally I'd glance at posts and noticed a lot of folks with problems had apps installed that I don't and attributed it to that. Thanks again!

 

I got a problem where I tried to print something in an app, and it doesn't matter what app, and my Avast kicked up a pop up saying that a suspected virus was sent to the virus Chest. It's a Name: CNB0265.dll at: C:\windows\system32\spool\drivers\x64\3, and a virus name:WINEVO-GEN(susp). I did a virus scan with Avast and MBAM and there's no virus. So I want to get the file out of Quarantine and can't. SO, I figured I'd just do an AX64 restore to the previous snapshot. I did, successfully. However the problem is still there, so I restored to a snapshot a week old, and the problem is still there. So I did another successful restore to still an earlier snapshot, and as I click on an app to print I still have the problem. I figured that if I restored behind the problem, I would eliminate it but I can't. Does any one know why the problem re-occurs? Thanks in advance for any help.

 

Hi twl845

I would say it is a false positive being reported by avast perhaps, also, keep in mind if you are running avast in self protected mode, meaning it protects its own files and registry keys, etc. from potential tampering, it is unlikely restoring a snapshot only in windows with AX64TM will not be able to remove it due to avast self protection is what I suspect. if you restore outside of windows with an image, that would/should work.

Self protected mode of many anti viruses can cause problems in other areas especially during some software installations, because certain registry keys may be protected that must be written to, etc., and the protected modes can interfere with certain operations.

Also, does your file by chance have an underscore in it...i.e., CNB_0265.dll ? I took a look at this and I believe it is a Canon inkjet printer driver?

In any case, i would try and temporarily disable or turn off avast self protection mode, then try and delete the file or restore the file from quarantine, if that fails, then perhaps try another snapshot restore...if that fails, you may have to boot into your imaging recovery environment and restore a full image, or an incremental, as long as it is outside the OS.

i do not think you were infected with anything, but perhaps a false positive from avast. Have you tried to upload the file to virustotal and check it there? In any case, this does not sound like a legitimate detection from avast.

I recently was trying out AVG and it flagged 2 well known windows files as rootkits, I knew it was not at all true, but just an FP event. I have not run an AV for months and I was reminded how they can be a pain sometimes. try the above and see if it makes any difference. I may be wrong, but it just sounds to me like a possible error on avast detection. Just my thoughts

I hope you get it worked out.

Jim

 

1) if jims ideas fail (hope they don't) go to 2
2) have AX64 and Avast exclude each other well at least have avast exclude AX64.
3) if 2 fails ( 99% chance I fear) go to 4
4) uninstall AX64 and Avast delete all previous AX64 backups as they restore the problem
5) Decide which is more NB to your setup Avast or AX 64 as they both can be replaced
6) do a restart without either, h.ll you have op protecting you while all this occurs
7) clean up the register( cc leaner what ever) update the os.
restart and see if you can print
9) install a working image system and backup your setup and test it
10) install the AV of your choice from the top 5 from AV comparatives under 30 day trial.
11) insure the combo of imager and av work okay together.

good luck