using Try & Decide when restart is required by newly installed program

[blanikix]

Hello,

Can any out there help me with the following question?

I want to use Try & Decide to test some antivirus software on my system but I'm currently an an impasse.

I turn on Try & Decide and then install the antivirus software. After the antivirus software is installed it requires that the system be rebooted. Restarting the system means that I have to choose to apply the changes in the Try & Decide wizard. I'm unsure what will happen when I restart the system with the new antivirus software installed. If there's any problems after the restart, I would like to be able to return to the system state that existed prior to the installation of the anti virus software. So I am wondering you there is there any way that I can avoid having to apply these changes to the system?

I know I can of course choose to have Try & Decide load on startup. And then this would protect the system from any problems that would arise after it has been restarted. However this doesn't allow me to go back to the system state that existed prior to installing the antivirus software because restarting the system would mean that I would have to apply the changes when the antivirus software asks me to restart the system .

Thanks for the help

[como]

You have found the problem that regular posters reported when TI11 was released, a feature ? that hasn't been thought through.

[blanikix]

Yeah, I kind of figured that that was the case.

This is disappointing. Especially given the fact that Acronis uses antivirus installation as an example to explain to potential customers how T&D can be a useful feature in TI11.

[DwnNdrty]

You can achieve the same thing that "Try & ThenDie" does by creating a Windows Restore point before you install the software you want to try. After you uninstall the software then restore the OS using the Restore point you created.

[blanikix]

-{ Quote: "You can achieve the same thing that "Try & ThenDie" does by creating a Windows Restore point before you install the software you want to try. After you uninstall the software then restore the OS using the Restore point you created." }-

Ah ha! Good idea!
Thanks

[laserfan]

I like to make Windows Restore points, but you might want to take a look at the WhyReboot utility (http://exodusdev.com/products/WhyReboot/), which tells you why Windows wants to reboot:

-{ Quote: "WhyReboot is a small (~100KB) Windows application that helps you decide whether to reboot your computer after running an installer. It does this by displaying a list of "pending file operations" (rename, delete, etc) that will occur after rebooting your computer. Quite often, no reboot is really needed." }-
Found this on somebody's "must-have utilities" list and it looks like something that would be very desirable if you do a lot of install/uninstall ops.

[shieber]

Just be careful of the caveats and not the limited circumstances in which it would be appropriate to avoid rebooting.

[pratzert]

How about using Rollback Rx and taking a snapshot.

If you don't like the software, you can easily restore to the point prior to installing the Anti-Virus software. ( AT least... I THINK you can, I have not installed my RollBack Rx yet.)

Tim