Discussion in 'backup, imaging & disk mgmt' started by Isso, Jan 18, 2013.
Many thanks Pete! Will give it a go.
Unfortunately , 1_3_7 did not fix the error.
Don't give up on AX64 yet. Yes, some rough spots, but as a long-time FD-ISR zealot, I'm really happy with AX64. Keep troubleshooting. There's a lot of help here.
Have you submitted a support ticket? Probably a good idea at this point.
Hi Seven64. It's not clear as to whether you are still working with the same snapshot chain that was taken while FD was installed?
Just to erase any unwanted complications, i would rename the existing "AXTM" folder to something like "AXTMold" and then redo a new snapshot. AX64 will recreate a new "AXTM" folder and a new baseline. Try restoring now and hopefully your error will be gone.
I wanted to play/test another recovery program. I CANNOT UNINSTALL AX64. I've done this several times before, no problem, and yes, I uninstalled the "pre-Boot" thingie first then rebooted. But for some reason it will not uninstall this time. I am using the very latest beta, 19, on a Win7 system.
HELP and thanks,
EDIT: Should have mentioned, I had ALL of my many security programs turned off when I attempted this.
Arcadia have you tried uninstalling in safe mode?
What about going back in time to before you had latest version, do you have a timeline to do that?
Hello Acadia...Awhile back I had a complete uninstall problem with AX64 and found Revo Uninstaller Pro took care of it. HTH
I did as you said, plus made a new recovery disk and the same error-99967.
Sent my logs in yesterday, no response yet.
Restoring while windows is working (hot restore?) works, just not through the recovery media.
If this is for real, then this is really
Anyway, if the hot restore works, maybe for the time being just do hot restore?
On a different note. A while back Pandlouk posted instructions on how to make FDISR and AX64 live together. Part of it meant excluding the map file in the System Volume Folder.
I tested this with the new Raxco InstantRecovery, and the exclusion is no longer necessary. I noticed in the log file the first attempt to read the file failed, but then the ISRCopy just elevated privleges and made another attempt and it was successful.
I think I have about given up on AX64.
I am running W8.1-64.
I have 2 HDD’s. “C” which is my system, “D” is where I am backing up to. Both are identical 1 tarabyte drives.
I added a USB thumb drive which I use as my AX64 boot drive for restoring proposes.
I can make backups just fine.
If I reboot to my thumb drive, I always get a warm restart which ends with the screen telling me that I had a boot failure and giving me options to insert my CD for repair, set my computer to default settings, etc.
I get these results form versions 1.2.1120 and 184.108.40.206
When I install a new ver of AX64, I always uninstall the program and clean the destination HDD and the USB thumb drive first.
This utility worked 100% on Windows 8. It have never worked on Windows 8.1.
Whoaaaa, Peter, way to go. Now you've got my brain churning, again.
Pete, are you saying that AX64 and RIR are co-existing? And if so:
Would you be running both of these side by side as backups to your backups?
Do you see the anchoring aspect as a big advantage, and in your view, why?
Yes at this point, I do think AX64 and RIR can coexist.
I am still figuring out how I'd use them. Right now I am beating on them to see what if any limitations there are. That will help figure out how I might want to use them together.
I never did use data anchoring. I only ever had to FDISR/RIR snapshots, and the 2nd one was only a place to go to to restore an archive.
Yeah, maybe I overused anchoring, still not sure. On one hand I liked the idea of snapping back in time when necessary without losing any changes to my data (docs, spreadsheets, photos, I even anchored all my Thunderbird email folders) and it worked. ;
on the other hand, not sure what's on the other hand.
Now, I oversee my wife's laptop (one hard drive with OS/programs/data); and my PC with data drives separate. Mine, I'd not anchor anything. But the laptop, I guess I'd still consider.
I do really like the speed and ease of AX64!
This is for real.
I could do that (hot restores) with FirstDefense, reason I bought AX64 was for cold restores.
I use BlackViper's "Safe" configuration. Is there any service that should always be set to Auto that might be interfering with the restore media, such as Volume Shadow Copy (was set to manual)? Just a thought.
Seven64, your RESTORE MEDIA doesn't use your live Windows OS, it uses its own (usually WinPE if created with AX64). Any settings you have in your LIVE OS shouldn't affect the restore media's capability to work.
Thanks, just trying to rule out possibilities.
Having now removed AX64 beta 19 from my PC windows 8.1, can anybody please tell me how to remove AX64 from the boot menu.
I have tried EasyBCD but cannot find it listed.
Surprising that EasyBCD is not listing it in the second menu on the left, so that you can delete it from there.
You have two choices:
1. Reinstall beta 19, uninstall the boot menu and then uninstall the beta 19.
2. Or try Visual BCD Editor and see that it shows up there and you can uninstall it through Visual BCD Editor.
Here is the link to download the Visual BCD Editor:
Finally got cold restore working, you were very close.
I booted back (to a very old snap-shop) with FD, did not uninstall FD, installed AX64 made a backup and new media (not sure if this was required).
Working so-far, might uninstall FD program after I export my FD snap-shops just in-case.
I am indebted to your subtle comment regarding second menu left.
I was looking at the initial page which turns out to be View Settings and has 8 (unexpectedly) entries listed none of them AX64.
The second menu does. Thank you very much and also for the thoughtful link, not now needed.
You are welcome!
P.S. Sorry to misspell your name earlier. My bad!
Separate names with a comma.