Uninstall Disk Director 10 from Win 7

Does it actually run? I'm surprised if it does.

If you wish to use 2239 0r the later 2288 (which won't let you install on W7) it should be from the rescue CD or ISO.

It won't automatically align sectors on 2048 boundaries.

This won't be a problem if your Vista system was originally on a disk that was partitioned by XP. If your drive has a separate 100MB partition to the main C:\ , then it has been partitioned by Vista or W7 and is in the NEW format.

At the moment I can only suggest trawling registry for DD10 references and deleting them, once done delete all the program files. Make sure you have a made a copy of registry or made a complete disk/partition image, before beginning in case the registry fiddling goes wrong.

It would also be worthwhile waiting a bit, if you can, to see if any one has an easier alternative.

Please tell Acronis Disk Director is installed without problems and works in the system Windows7?
(Not about boot and work with the boot CD)

Vasiliy,

Disk Director 2288 and 2239 will not install in Windows 7. The version prior to 2239 will, but there are some things that might not work as expected.

DD11 is in beta at the moment and is Windows 7 compatible.

I don't know when it will be released.

Thanks for such a quick response.
So we just need to wait when the next version of the program.

Hello,

Vasiliy, let me shed some more light on your concern.

Indeed, Acronis Disk Director 10.0 doesn't support Windows 7, however, as Colin mentioned, you still can use it with its bootable media.

Additionally, we've started a public beta-testing of the next version of the software. If you want to participate in the beta-testing, please visit this link.

Please let me know if you have any additional questions.

Thank you.

The beta program has expired and no longer available.

So its's over a half year since Windows 7 has been released and Acronis has not been able or willing to make DD10 compatible?
And of course all customers will have to pay for the successor, right?

Btw: I installed DD 10.0.2161 a few months ago and it worked, but after some Windows updates it does not even start. Deinstallation is not possible.
So I am stuck with a non working software I paid for, and teh question remains:

How do I manually uninstall DD and get all its bits and pieces?

I also have DD10 build 2239 installed on my Win 7 64 bit. It will open and run but will not perform any disk functions. I am unable to uninstall it. Am I to understand that the only way to remove it is to search my computer and registry for any references to DD10 and manully delete them.

Hello Klaus and Andrew!

Thank you for your comments.

Unfortunately due to the fact that Acronis Disk Director 10.0 doesn't support Windows 7, about which we are constantly notifying the community, there are no instructions for manual uninstallation available. So the best way to uninstall the product is to try removing it from Add and Remove programs.

Also you can try to the following: 

1. Deactivate OS Selector
2. Remove SnapAPI from the registy
3. Remove the rest of ADD files from the machine

It should help to resolve the issue.

Should it be present, please kindly gather Acronis Info and contact support directly. 

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you.

Thank you.

After I installed Disk Director 10, I realized that the version 10 does not support Windows 7. Then, I uninstalled the version 10 using Add and Remove programs. It seemed to be successfully uninstalled. But, when Windows 7 was rebooted, it is crashed and is not rebooted. The system just continues to be rebooted. What do I have to do?

If you can boot into Windows SAFE mode (press F8 key whilst booting) or W7 offers you the option of running safe mode due to not shutting down correctly, you can then perform option 2 in post #8.

Did you install and activate the OSS?

Thanks, Colin B. It really works.

I had the same trouble of using Disk Dir 10 with build 2288 in Win 7

So, I went back to DD 10, Build 2160 and it worked.

OK Acronis, realize Win 7 is here to stay.

NOTE: Build 2288 works in Win XP.

If you use DD 10 on any disk with Windows 7 - or, indeed, that MIGHT at some stage in the furture have Windows 7 installed on it - then you are playing with fire! Yes, the earlier versions of DD 10 may SEEM to work - & of course there's nothing to STOP you using a DD 10 boot disk from any version. But there may be serious repercussions ...
I found this out the hard way - when trying out Windows 7 Beta. I used a DD 10 boot disk to create an NTFS partition before installing Windows 7 onto it. Initially all seemed fine. But after a few days, I tried to install Visual Studio 2010 Beta. The Visual Studio installations involve copying a very large number of small files, amongst all the other installation issues - which make them very testing of file systems. My attempts at installing it failed repeatedly. The standard reason given for this is a bad download, so I downloaded it again; still failed. I tried copying the Visual Studio installation DVD onto the hard drive first, & installing from that. It still failed.
The failures were somewhat unusual, in that I kept getting messages reporting file system errors; & others where, for example, Visual Studio claimed it couldn't write to a folder, that appeared to be both present & writable. Anyway, after a while I gave up trying to install it. But then I found that more file system errors started appearing. For a while, I could apparently fix them with Chkdsk; but then they started becoming more & more frequent, until the entire Windows 7 installation became unusable.
I found I couldn't even back up the installation with Acronis TI - or anything else for that matter. I had to trash the partition, & reinstall from scratch, making sure that I let the Windows 7 installation create the NTFS partition in the first place. Then, all was well.
On looking around the net, I eventually found just a very few other reports of "things going wrong" with NTFS partitions created by DD 10 & then having Windows 7 installed on them.
So the message seems to be: whatever you do, DON'T use DD 10 to create an NTFS partition, if you might ever use Windows 7 on that disk. If you do, you may think that all is well; but you will almost certainly find that some time later, the whole installation will fail with these file system errors.
Incidentally this is NOT the same issue as that regarding sector sizes.
I'm not sure whose fault this issue is - clearly Windows 7 is making some sort of assumptions about NTFS partitions that Vista & XP didn't.
Also, note in view of the above comments that Acronis's advice not to use DD 10 on Windows 7 (and indeed preventing the last versions from installing on it) is NOT just a matter of trying to sell DD 11. I agree with others who have noted the sad limitations of DD 11 functionality compared to DD 10, but at least it seems to be safe with Windows 7. DD 10 DEFINITELY ISN'T! YOU HAVE BEEN WARNED!

Here it is ten years later and I ran across this thread because the problem with Disk Director 10 (DD 10) came up in the process of upgrading a computer from Windows 7 to Windows 10. The same compatibility issue appears to exist with the current operating system as it did with Windows 7, including the OS becoming unbootable after uninstalling DD 10. I wised up and started making image backups, and in the process of investigation, discovered the following:

The boot problem on my computer appears to be brought on by either deleting snapman.sys, disabling it in the registry, or both. After using the DD 10 installation disk to uninstall the software, I found that I was able to get Windows 7 booting again by using the "Last known good configuration" option in Advanced Boot Options. Unfortunately, that utility does not exist in Windows 10, but through Googling I found out that it functions by restoring the driver and registry configuration. So for Windows 10, I ended up manually deleting the DD 10 program files and start menu references, but leaving the snapman.sys and the registry alone (except for manually deleting DD 10 from the uninstall list as described here). That allows Windows 10 to remain bootable on my computer, while preventing DD 10 compatibility issues from making trouble by being executed.

I don't know whether leaving DD 10's snapman.sys and registry references in place will create problems if I install the current version (12.5) of Disk Director, as I haven't tried that yet.

There are three steps to manually remove the snapman service.

1. Delete the snapman service from HKLM\SYSTEM\CurrentControlSet\Services.

2. Delete snapman.sys from C:\Windows\System32\Drivers. Delete snapapi.dll from C:\Windows\System32.

3. Remove snapman from the Upper Filters list at HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318} and HKLM\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}.

This will solve the bootability issue. Step 3. is what you missed. 

I wouldn't trust installing DD 12.5 with the DD 10 snapman service in place. The DD 12.5 installer may not overwrite snapman.sys and snapapi.dll. If you do decide to go that route, note the version numbers of snapman.sys and snapapi.dll before you do the install. If you don't get higher version numbers after the install, you could have problems with DD 12.5. 

Paul, thanks for the reply. The three steps you outlined resulted in Windows 10 becoming unbootable again, so I restored from my image file.

I then tried installing the demo version of Disk Director 12.5. There were a couple of glitches in the installation process, including a BSOD with a stop code of "ATTEMPTED SWITCH FROM DPC," but the subsequent forced reboot was successful. Furthermore, the result was an apparently functional installation of DD 12.5, oddly enough. The old snapman.sys (version 3.0.0.303) was gone, replaced by version 4.7.0.2592. There was also a file called "snapman2592.sys," which I suspect was a leftover from the glitches in the installation process.

I then tried uninstalling DD 12.5, and this was successful, with the system still booting normally. Snapman.sys is gone, although snapman2592.sys was still there. I manually deleted that and snapapi.dll, and the system stll reboots normally.

After I save a new image file, I'll try installing the DD 12.5 demo again, to see if the installation goes normally this time. If so, then I'll do some further testing before deciding whether to buy.

That is strange. Did you notice what the reason was on the BSOD screen? Did it refer to snapman.sys?

You may be right about the reason for snapman2592.sys. It looks like Acronis is now saving the old version of snapman.sys during an install and adding the version number to the file name. I looked at a system with both True Image 2020 and Disk Director 12.5 and I see snapman.sys version 2632 and snapman2605.sys. This makes sense because True Image 2020 was installed last.

The first sign of trouble during the first DD 12.5 installation was a message saying "Installation Incomplete," and "The installation was interrupted before Acronis Disk Director 12.5 could be installed. You need to restart the installer to try again." Restarting the installer led to the BSOD. It didn't stay on the screen very long before the reboot began, but I didn't see a mention of snapman, just the stop code I quoted in my last post.

After uninstalling and saving a new image, I tried installing again, and I got the same "Installation Incomplete" message. This time I checked the status of the machine without restarting the installer, and found that it had already succeeded in creating an apparently usable installation. The snapman2592.sys was not present this time, so on the previous installation, I'm guessing that file was a result of restarting the installer (which I didn't do this time).

By the way, I just now tried installing the DD 12.5 demo on the Windows 7 partition of the same computer, and it installed with no error messages, in spite of the fact that Windows 7 still had the DD 10 snapman file on it. I guess there must be something about my Windows 10 installation that bothers the installer.

The only thing I can think of is that left over folders in the Temp area can cause problems with the install. Try deleting all from Temp.

It's not essential to solve the remaining mystery on this computer, because if I end up buying, it's not the machine that I will be keeping it installed on. It just barely meets the minimum system requirements for 32-bit Windows 10. Instead, I would be keeping DD on another computer, which is 64-bit and substantially exceeds the minimum requirements. I did a trial installation on it today and there were no errors of any kind. That, plus the fact that DD 12.5 handled the uninstallation problem on the 32-bit machine, increases my level of confidence in the current version.

Thanks for your help!