Skip to main content

Cannot Activate TI Home 2010

Thread needs solution

Hi, I had Seagate Disc Wizard installed and decided to go for the upgrade. Purchased the upgrade earlier this week and couldn't get it installed. An un-install of Disc Wizard caused my machine to crash during subsequent boots until I rolled it back to the previous check point. TI Home is now installed and I'm ready to enter the serial number, however the product activation dialog wants two serial numbers. Is one of these the serial of the Disc Wizard serial, if so, how can I recover the serial number of it to allow me to continue?

Andy

0 Users found this helpful

Hello AndyB,

Let me shed some light on the issue.

You are absolutely correct, Seagate DiscWizard has a built-in serial number, so should not be removed prior to the installation of Acronis True Image Home 2010.

I may recommend you to download Seagate software from their web site, install once again and activate Acronis True Image Home 2010.

Please reply to this thread if the issue still persists, I'll be glad to assist you further.

Thank you.

Ilya,

I've tried re-installing Seagate DiscWizard but it won't install as it has found a later version installed

Attachment Size
31212-89362.jpg 26.87 KB

Any update on this?

You may want to try this approach http://kb.acronis.com/content/7533 to get rid of the current installation completely.

Hello,

thomasjk, thank you for your help.

AndyB, if you have this error message after you've uninstalled Acronis true Image, please follow thomsjk's recommendation and use Acronis Clean-Up Utility to get rid of all traces of the previous installation.

After that, install Seagate DiscWizard again.

Please reply to this thread if the issue still persists or if you have any further questions.

Thank you.

I've tried to do what you asked. I unistalled TI Home and run the cleanup utility. The machine does not reboot. It is now in a continual boot cycle like before and safe mode does not work. It crashes and reboots after mup.sys is loaded.

Looking throught the forum articles here suggests that the Snap API may be the problem. I'm going to try and get a copy of the driver to copy into the crashes machine.

Any update. I can't use this machine.

I've had an unusable computer that is stuck in a continual reboot recycle. Does nobody in Acronis have the slightest idea how annoying this is and have information about I can repair it? This issue is now over 2 weeks old and not even an acknowledgement :-(

Hello AndyB,

We're terribly sorry for the difficulties you've experienced.

I recommend you to collect AcronisInfo tool output and submit a request to support. We'll definitely help you.

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

The machine does not startup. I would need to run this tool from the recovery console. Is that what you want me to do?

Andy B,

Which OS are you using?

There appear to be a number of causes to MUP.SYS failing (this is an MS system file).

If this is an XP system then there are a couple of things you can try.

Insert the XP install CD and log into the recovery console:

1. Run chkdsk from this prompt. If that doesn't solve the problem go onto number 2.
1a Type in disable mup.sys and reboot.

2. at the command prompt type in expand YOUR_CD_ROM_DRIVE_LETTER:\i386\mup.sy_ file C:\windows\system32\drivers

3. Run an XP repair install - downside of this is that it will wipe out all your MS updates and service packs that aren't on the install CD - all your registry entries are kept though.

4. If you are using a PS2 mouse, try using a USB one, when the system hangs at boot time, unplug the mouse - your system may now boot into safe mode or it may not.

Here is what Microsoft have to say on the subject.

http://social.answers.microsoft.com/Forums/en-US/xphardware/thread/bbd4…

There are a further 227 suggestions on the Microsoft knowledge base site - good luck!

The mup driver (Multiple UNC Provider) may not be the one at fault, it might just be the last drive loaded before Windows decides it's had enough.

Hi Colin, thanks for the suggestions. I'm quite sure that MUP.SYS is not the problem. It's just the last driver to load.

I'm guessing that the snapshot drivers or API are not properly installed and since all disk access is redirected through this driver Windows doesn't know what to do and stops.