If not I have a restart TI Ver 11 CD and backup prior to this horrible upgrade. I guess I will start TI 2010 and tell it to execute the scheduled task now and then make a restart CD to see if it will find my USB drive. Then closed Disk Director 10 and this time TI 2010 came up without that reboot message. Then closed TI 2010 and opened Disk Director 10 and all was still good. I clicked on the yes reboot and after the reboot, I tried TI 2010 first and all was well.
(I can't figure out how to insert pic, but it is attached). After reboot I ran Disk Director 10 and all appeared okay in disk director, then I stopped disk director 10 and loaded TI 2010 and got the attached message telling me a reboot was necessary. Then I loaded Disk Director 10 and did a reboot. Went great TI 2010 run and allowed me to at least set up a scheduled task. Well first your step one requires a reboot after unloading the first product.Īfter loading TI 2010 and reboot, I went in and set up a task to run on Saturday and all that went well.
Guess I shouldn't have taken that long vacation and then I could have tested?Īnyway this did work with only one minor weird thing. I had the same problem, this is the first time I wasn't involved in the beta testing since I started with Version 8. Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. Reboot the computer to complete the changes.Īfter that please install the latest builds of the programs in thew following order: Then please delete the programs by means of Add or Remove programs utility or by launching the installation file of the program (select the Uninstall option in the main menu). You can learn more on how to download the latest build here. Please download the latest builds of the programs from our web site. The last digits will show you the build number.
Please make sure that you are using the latest builds of the programs (Acronis True Image Home build #6029 and Acronis Disk Director Suite 10.0 build #2239). You can find out the build number by making right-click on the installation package -> Properties -> Version -> File version. The encountered issue is caused by incompatibility issue within the programs of different builds.
0 kommentar(er)
