The Trial version of Acronis OS Selector is expired

Hi,

I have the same error report "the trial version of Acronis OS Selector is expired", although I have a full version of Disk Director Suite 11 installed.
And only THAT Acronis software, nothing else. After a month or so, this message appeared blocking any access to the OS Selector.
The only serious action I did during that month was updating the BIOS of my motherboard to the final version F6.
Here are the details of my computer:
Motherboard: Gigabyte GA-X48T-DQ6
CPU: Intel Core2 Quad Q9650
Harddrives: Seagate
Operating system: Windows 7 Professional up to date

Any help is very much appreciated
Thanks

From experience the only way around this is to uninstall and re-install/configure OSS, I had the same issue and this was the solution. I also had the same thing happen once when I did a restore of my system disk.

Thanks for your answer RayG,

After you reinstalled OSS, did the settings previously chosen remain, especially "hide a drive", or did you have to reconfigure completely OSS and in that case could you see the previously hidden drives with OSS?

Best regards
JamesBond770

No you have to do the set-up again - its a pain...

Partitions that were hidden stay hidden - you just have to make sure OSS is configured the way you want when you reinstall it.

OK, thank you very much RayG

Best Regards
JamesBond770

I had same problem. If a uninstall/reinstall is the only way to solve this problem I will leave it at uninstall and turn my back on Acronis and look for an alternative bootmanager. This OSS crap has caused me so much problems of unbootable systems it's a shame this ver was released as a product !

I have the same problem. Have deinstalled all Acronis Products (TrueImage and DiskDirector). Have done a frsh install of DiscDirector an OSSelector. The same Procedure three times. I alwas got the same result. After 15 days OSSelector expires.

Any Idea any help ???

Best Regards

Peter

I got the same problem.

Help us Acronis

Rune

Hello everyone!

I am glad to tell you this bug has been fixed in Update 1 which is coming soon.

Thanks to all of us for patience and participation.