Skip to main content

Drive Cleanser broken?

Thread needs solution
Beginner
Posts: 1
Comments: 0

Hello, am booting in with USB to a computer to wipe the drive. I am using the full Windows 10 backbone version of Acronis True Image 2016.

I get the error: The instruction at 0x00007FF83A65C9E7 referenced memory at 0x0000000070E2A200. The memory could not be written. Click on OK to terminate the program, and when I do, True Image 2016 craters and brings me back to the cmd prompt.

I also tried a different hard drive in the same machine, and also noticed that if I go into diskpart and clean the drive, then go back into True Image (even after restarting the machine), it will not even recognize the drive. What really? Just because there are no partitions, Drive Cleanser will not function?

Either this part of TI needs to go back to the drawing board, or it just won't function with certain hardware, which is not good either. I've used previous versions of drive cleanser in the past and not had this issue. What gives?

Tim

0 Users found this helpful
Beginner
Posts: 0
Comments: 2

I am having the exact issue myself when trying to boot off WDS or from a USB device. Any suggestions?

Forum Star
Posts: 60
Comments: 1413

NHBP IT...welcome to these user forums.  It is difficult for me to understand the original problem.  Here's what I think it is.  The user boots from USB rescue media which then launches the Linux version of True Image 1026.  The user then tries to launch Drive Cleanser which is when the program crashes.  Is that the problem that you have?  Or is the USB rescue media not booting at all?

In either case, I would recommend creating the WinPE rescue media, then giving it a try.

Regards,

FtrPilot

In reply to by FtrPilot

Beginner
Posts: 0
Comments: 2

I did create the rescue media, and I made it as a .wim file. I applied that to our Windows Deployment Service, and booted to it via PXE. I get the exact error that the OP listed. I also tried recreating the media, and using media that we had on a flash drive...all the same issue.

Forum Star
Posts: 60
Comments: 1413

Thanks for the further explanation.  At this point, I don't have an answer, but  I do have 2 recommendations: 

One of the MVPs have created a utility to generate a 32bit or a 64bit rescue media.  The link below will allow you to download the utility:

https://kb.acronis.com/content/59335

 

You could also try the 30 trial of ATI 2018.  With it, you can create a WinRE rescue media.  )To be honest, I don't know the difference between WinPE and WinRE.)

I hope one of these recommendations work.

Regards,

FtrPilot

Legend
Posts: 79
Comments: 16740

Take a look at webpage: 42 Free Data Destruction Software Programs which shows just many alternative programs are around in this area.

I personally have never used the Drive Cleanser utility part of ATI but have seen other posts in the forum where it hasn't been very good!

Randy, as far as I understand, WinRE is built using the Recovery Environment files from the computer where the Rescue Media Builder is running, so will include any specific drivers for that computer from that environment, whereas WinPE is a more vanilla built taken from the Windows ADK components and not personalised unless using such as the MVP Custom ATIPE script to do so.

Forum Star
Posts: 60
Comments: 1413

Steve,  Thanks for the info on RE & PE.

Beginner
Posts: 0
Comments: 1

I have an issue regarding my hard disk. I used the Disk Clearing program on my old SSD, it took more than 3 hours to finish so I decided to cancel it but now my computer is not booting properly with the hard disk. It automatically goes to Start Up Repair and then fails to repair anything. I would try to opt out of the Start Up Repair but it would just restart and do the same thing over again. I couldn’t reset the settings as well and trying to boot with Safe Mode doesn’t work as well.

Legend
Posts: 79
Comments: 16740

Joan Marie, welcome to these public User Forums.

Sorry to hear that your computer is not booting properly but will need more information to try to offer any help.

Have you got a full backup of your main Windows OS drive made before using Drive Cleanser?

When you selected the drive to be cleaned by Drive Cleanser, did you ensure that you picked the correct drive?  Drive Cleanser should not have affected your Windows OS drive unless that drive was chosen by error?