Certificate File Missing Or Corrupt In Ecd Burning (Emc9)

[Cadillac Mike]

I see all the posts. Not just this product but many other roxio products have this certificate file error. I can't clear the error, i uninstalled and cleared every registry entry, re-installed - got the MSI error, wiped it off the disk again, changed a setting in MSI to clear that error, re-installed again.

 

Still getting the certificate file missing or corrupt error.

 

I deleted the EMC9.rxc as per Brandon's suggestion in another thread. That didn't help. by the way, the file datestamp is the same as when i originally installed this back in 2009. I also copied the file from the original CD - still getting the error.

 

Why is it that MANY roxio products have this error, and what have you done to prevent it? If my wife gets this error - that's it, we're migrating to a different product that doesn't render itself inoperable for no apparent reason.

 

Is there a straightforward correction for this error? Why is this application so unstable, that even copying the license file from the install CD will not clear the error?

 

This used to work, now an unchanged certificate file is 'corrupt' (becausae it isn't missing) I just don't get it.

 

If i have to uninstall this again, it's not getting re-installed.

[grandpabruce]

I must admit that I do like it when I'm right...

 

Well, sonic / roxio DOES INDEED tie the application (at least this one and i'd wager most or all their others) to the volume serial # of the HDD.

 

In case anyone doesn't remember, volume serial # were instituted to reduce OS confusion over users swapping diskettes while operations were going on - NOT for mfrs to wrap up an application to a volume serial#.

 

Further to not disclose this and then to mask it with a certificate file missing or corrupt error is just plain rude.

 

I have never had one yet not install on another hard drive, but I have never used any stripped down OEM versions of the software.

[Cadillac Mike]

I have never had one yet not install on another hard drive, but I have never used any stripped down OEM versions of the software.

 

It's not that you can't install on another drive (for the same machine folks - let's not turn into bluebeards here!) it's that migrating to a new disk is prevented by having the application fail if the volume serial # is changed.

 

My package was a retail box, not an OEM version. granted it is not the full EMC9, but there are 3 pages of threads with certificate file missing or corrupt as the subject.

 

what happened to my other thread - did it get deleted or was it merged??? I made a one pager version without all the speculation for those that are still finding this out the hard way...

[Jim_Hardin]

I am going to close this Topic as it only applies to one specific condition (rare?) based on a long out of production version on an unsupported OS

 

As always, if anyone feels there is some need to open it, let me know and we will open it up

[Jim_Hardin]

The version you have was pretty short lived, less than a year. It has since moved on with 2 more versions bringing the total to 3

 

If it keeps breaking, then there is something on your PC that is doing it! Probably AV or a Reg Cleaner

 

The device is still good but it might be time to upgrade your software to one on the Creator 20xx versions.

 

Of course you will need to check closely to make sure your PC meets the specs of those.

[Cadillac Mike]

The version you have was pretty short lived, less than a year. It has since moved on with 2 more versions bringing the total to 3

 

If it keeps breaking, then there is something on your PC that is doing it! Probably AV or a Reg Cleaner

 

The device is still good but it might be time to upgrade your software to one on the Creator 20xx versions.

 

Of course you will need to check closely to make sure your PC meets the specs of those.

 

Hello Jim,

 

I remember reading your posts a year or so ago. can't remember why, I think it was over some error my wife was encountering.

 

It broke one time, not several. I tried several times to eradicate the install and re-install.

 

I didn't know that i needed to erase all registries with Sonic in it and did, now it is at least loading after a re-install. BTW, There were two more locations with roxio and sonic enties than the complete uninstall listed roxio web page ilisted. I cleaned them up too maybe that's PART of why it wouldn't work when i tried to reinstall it earlier.

 

I made a further search on the forums and discovered that someone else found out that roxio products are tying themselves to the Hard Drive volume serial #, and if the disk on which roxio is on has a different volune #, it will fail with the certificate file missing or corrupt error.

 

Nice insiduous little trick there roxoi / sonic. It's not missing or corrupt, it's just running on a different HDD. This is stuff that I absolutely despise.

 

This also confirms what happenned to me. I changed my HDD out, and that's when Roxio stopped working. I also installed a disk utility right afterwards, and thought that was what broke roxio, but after needing to re-clone because of a disk error, and NOT installing that disk utility, roxio still refused to start with the certificate file error. Then i found the posts on the volume #, and the MS utility to re-write the volume serisl #, which is what i'm going to do with my backup drive. That'll be another week long process.

 

I re-installed that disk utulity and roxio still loaded, so i'm fairly convinced this is what happened in my case.

 

Not a real good feeling on roxio over this. All i needed to do was burn an iso onto a CD to install an MS utility. Took me over a week. If this is how roxio treats their paying customers, i'm not likely to buy any newer version of their products.

[cdanteek]

What version do you have and what operating system and service packs are you running it on?

 

http://forums.support.roxio.com/topic/58910-which-version-do-you-have/

[Cadillac Mike]

I'm not sure how many folks will be helped by this, but it is certainly faster than the de-install, eradicate registry entries and re-install method.

 

If you upgrade your HDD, i.e., clop / clone it onto a larger disk, roxio products (many not sure if all) will fail to load with the certificate file is missing or corrupt error. This is because when it installed, roxio tied itself to the HDD's volume serial number. Then after you try to run it on the new HDD, it fails if the new HDDs volume seriam # does not match the original HDD, and not all clon / sopy methods will copy over the original volume serial # to the new disk.

 

Not an overly friendly act and certainly not one disclosed anywhere, especially since we're supposed to have a backup of items we purchase, which the license provides for.

 

I also noticed on the dozens of posts here that no one from roxio ever asked if the HDD had been changed, and i'm sure they know about the install routines.

 

Well, there IS a work around. Microsoft has a volume id changer software utility free to users. ssearch for ms volume id changer software and it's right on an MS page.

 

You will need your original HDD's volume # so use the VOL command and write it down!

 

Then run that and follow the instructions, and DONT have both disks with the same vol # in the computer at the same time because you don't know what winblows will do!!!

[cdanteek]

I'm not sure how many folks will be helped by this, but it is certainly faster than the de-install, eradicate registry entries and re-install method.

 

If you upgrade your HDD, i.e., clone it onto a larger disk, roxio products (many not sure if all) will fail to load with the certificate file is missing or corrupt error. This is because when it installed, roxio tied itself to the HDD's volume serial number. Then after you try to run it on the new HDD, it fails.

 

Not an overly friendly act and certainly not one disclosed anywhere, especially since we're supposed to have a backup of items we purchase, which the license provides for.

 

I also noticed on the dozens of posts here that no one from roxio ever asked if the HDD had been changed, and i'm sure they know about the install routines.

 

Well, there IS a work around. Microsoft has a volume id changer software utility free to users. ssearch for ms volume id changer software and it's right on an MS page.

 

You will need your original HDD's volume # so use the VOL command and write it down!

 

Then run that and follow the instructions, and DONT have both disks with the same vol # in the computer at the same time because you don't know what winblows will do!!!

 

I've cloned failing hard drives with full Roxio Suites in the past and had no trouble at all using Acronis TI Software.

 

Why would anyone ask if a HD had been replaced? You folks should provide software name and version #, operating system it's run on, and any other important details!

 

So tell us what was your cloning software and detailed method of cloning your HD?

[Cadillac Mike]

Running winblows XP with SP 3 the AV is symantec endpoint.

 

I have the red box retail package Easy CD & DVD burning. I think it is a subset of easy media creator 9. That would fit in with the time frame of when i bought it. It worked until i changed the HDD out as noted in my above post.

 

I decided to re-try one more time, i had to get if off the HDD anyway since it was just taking up space.

 

Like i said i got it to load by removing all sonic and roxio references in the registry after un-installing. I also deleted all the hidden directories as noted.

 

It is worth mentioning that a top to bottom search of the registry showed TWO additional places where there are roxio and sonic key entries. I deleted those as well and ran a final search on both words to ensure there were no more entries. Then in disabled AV via MSCONFIG and re-installed it. And it loaded.

 

Why roxio finds in necessary to make hidden directories fail me. Why they tie the install to the HDD volume serial sumber doesn't fail me, it just frosts me.

[Cadillac Mike]

I used acronis disk director to copy the primay and the IBM_Service partitions onto a new drive. I then have to update the MPR and deal with any HAL.DLL errors that it may throw at me.

 

I copied my original HDD onto two new identical HDDs. I have not done anything to the second HDD, and will boot that one tonight to verify if indeed the roxio product is tied to the volume serial # of the original HDD.

 

One reason you might not have encountered this is because acronis TI may actually copy the volume serial # over to the new drive. I'll find that out too when i eventually get acrois true image to make a clone the way i want it to. Disk director probably does not copy the volume serial #. This should all sort iteslf out in a day or two.

 

Again, roxio worked (still does) on my original HDD. It refused to load when i tried to start it from the drive i cloned onto.

[Cadillac Mike]

I've cloned failing hard drives with full Roxio Suites in the past and had no trouble at all using Acronis TI Software.

 

Why would anyone ask if a HD had been replaced? You folks should provide software name and version #, operating system it's run on, and any other important details!

 

So tell us what was your cloning software and detailed method of cloning your HD?

 

A better question to ask is WHY IS ROXIO TYING THE SOFTWARE TO THE HDD VOLUME SERIAL #?????

[cdanteek]

A better question to ask is WHY IS ROXIO TYING THE SOFTWARE TO THE HDD VOLUME SERIAL #?????

 

 

It didn't in my case.

 

You would have to open a support ticket and ask them.

[Cadillac Mike]

It didn't in my case.

 

You would have to open a support ticket and ask them.

 

I wouldn't be so sure. You used true image, which i suspect copied the original HDD volume serial # over to the new drive.

 

I used disk director and copied the partitions over individually.

 

i will find out later when i boot my original HDD, write down the volume serial #, then put in my 2nd cloned disk (with the non-working roxio), change the volume serial serial # on that disk to match my original and then see what roxio does.

 

I already fixed it on my first cloned disk by the uninstall - eridate - re-install method, but that takes forever.

 

I'll post the results here.

[cdanteek]

I wouldn't be so sure. You used true image, which i suspect copied the original HDD volume serial # over to the new drive.

 

I used disk director and copied the partitions over individually.

i will find out later when i boot my original HDD, write down the volume serial #, then put in my 2nd cloned disk (with the non-working roxio), change the volume serial serial # on that disk to match my original and then see what roxio does.

 

I already fixed it on my first cloned disk by the uninstall - eridate - re-install method, but that takes forever.

 

I'll post the results here.

 

You didn't clone your HD. I see why your having problems.

[Cadillac Mike]

You didn't clone your HD. I see why your having problems.

 

 

Yeah, I'm finding out that disk director and XP do not get along as well as the old w98 and Partition magic!!! I have true image - might as well enter their 87 million byte product key and install that.

 

All this is because i've had HDD failures in the past (they do break eventually) and i don't want to spend weeks with a start from scratch from the ThinkPad recoveryt CDs...

 

Instead I'm spending MONTHS figuring out a foolproof clone process and the various pitfalls therein. I need to have this down to a science to upgrade my wife's HDD. No room for errors there!

[grandpabruce]

 

[snip]

 

Why they tie the install to the HDD volume serial sumber doesn't fail me, it just frosts me.

 

I have never heard, or seen, that Roxio ties the install to the hard drive volume serial number. I haven't had a problem installing any Roxio software on a hard drive, other than the original hard drive that it was installed on.

 

Possibly, the source that says Roxio software is tied to the hard drive serial number is a bunk source?

[Cadillac Mike]

I have never heard, or seen, that Roxio ties the install to the hard drive volume serial number. I haven't had a problem installing any Roxio software on a hard drive, other than the original hard drive that it was installed on.

 

Possibly, the source that says Roxio software is tied to the hard drive serial number is a bunk source?

 

I will verify that tonight. I made two disk copies (not true "clones" as per the other post), i fixed one with the unilstall - eradicate - re-install method. The other is sitting in a case. I'll check volume serial #s try to start roxio in the "cloned' HDD, reset if different from the orifinal HDD serial # with the MS utility and then see what happens.

 

IF the volume serial #s are identical already - and i HIGHLY doubt that is the case, then I'm barking up the wrong tree.

 

That post is on this forum somewhere...

[Jim_Hardin]

You are mistaken regarding the HDD magic that you claim...

 

In your other post you say you are Cloning Partitions rather than the actual disc. Not going to work!

[Cadillac Mike]

You are mistaken regarding the HDD magic that you claim...

 

In your other post you say you are Cloning Partitions rather than the actual disc. Not going to work!

 

It works for everything else; roxio was the only major application that refused to start after I did the partition copy. It IS a PITA because the MBR needs to be re-written and sometimes BOOT.INI and HAL.DLL, but if you know what you're doing, it works. I have 4 running "cloned" disks that i made and they all boot in my T30.

 

As stated, I'll verify all this tonight, because i have a 2nd 320GB HDD that i cloned my original HDD to and I haven't done anything to that one.

[Jim_Hardin]

I have clone 3 PC's each month for some time and have yet to have any application that does not work, including many Roxio Suites and programs!

 

I do the ENTIRE disc not the partition.

 

If you and another person have had a problem with it, it isn't enough for any software manufacture to worry about Again you are having a problem with a product that has been out of production for several years along with an OS (XP) that is no longer supported

 

Not knocking your software at all, just keeping it in proper perspective

[Cadillac Mike]

I have clone 3 PC's each month for some time and have yet to have any application that does not work, including many Roxio Suites and programs!

 

I do the ENTIRE disc not the partition.

 

If you and another person have had a problem with it, it isn't enough for any software manufacture to worry about Again you are having a problem with a product that has been out of production for several years along with an OS (XP) that is no longer supported

 

Not knocking your software at all, just keeping it in proper perspective

 

 

all agreed Jim,

 

Here's the post that leads me to believe the HDD volume serial # is tied to roxio:

 

http://forums.support.roxio.com/topic/33915-roxio-does-not-work-on-cloned-computers/page__p__180779__hl__certificate+file+missing+corrupt__fromsearch__1#entry180779

 

A few items to note.

 

OP used some MS disk utility, i used acronis disk director with a partition copy, and you clone the entire disk at once. I'm pretty sure that your method preserves the original volume serial #, and i'm equally sure my method does not. And i'm pretty sure the OP's method does not.

 

OP wanted to clone for multiple machines. I want a plug-in ready backup disk for my single T30.

 

I have acronis true image, i just read somewhere that it will not clone to a smaller drive - well, i needed to do that, so i went out and got acronis disk director. But someone else told me i could use TI to clone to a smaller drive as long as the used space on the source was less than the space on the target, so i'll try it again.

 

Yes it's an old program. I have many that are MUCH older that i use. And from what i read, the newer versions are even worse in this regard, as is winblows vista or 7 compared to XP.

 

Like i said, I'll get to the bottom of this tonight.

 

And I STILL think it is INSIDIOUS for an MFR to wrap its apps around an HDD Volume serial # and then hide that fact.

[Jim_Hardin]

Mike, I have done all I can.

 

some see Dragons where others only see Windmills

[Cadillac Mike]

Mike, I have done all I can.

 

some see Dragons where others only see Windmills

 

Jim, It's been a good discussion. I now understand perhaps another reason to use a true cloning process rather than a partition copy method. Not sure i like the reasons why though. Like i said I'll know more tonight. I may have to eat some words, but i don't think so.

[Cadillac Mike]

Well, I was right, I must admit that I do like it when I'm right... (my wife hates it though!)

 

Sonic / roxio DOES INDEED tie the application (at least this one and I'd wager most or all their others judging from the threads) to the volume serial # of the HDD.

 

I booted my original Hitachi 100 GB on which ECDC / EMC9 worked correctly and wrote down the volume serial #. Checked to see that EMC9 was still working. Shut down, put in my 2nd WDC320GB which EMC9 doesn't work on (remember I fixed my 1st WDC320 by the uninstall-eradicate-re-install method). Tried to start EMC9 and got the cert file error, which was expected. I then checked its volume; it was different because the first part of the # is based on the current date.

 

I changed the # to match the original HDD and rebooted EMC9 still gave me the error - I mistyped the first time and thought oh no this can't be, but a check showed my poor typing was the issue. changed it this time to really match the Hitachi, and rebooted.

 

And EMC9 loaded right up.

 

In case anyone doesn't remember, volume serial # were instituted to reduce OS confusion over users swapping diskettes while operations were going on - NOT for mfrs to wrap up an application to a volume serial#. Further to not disclose this and then to mask it with a certificate file missing or corrupt error is just plain rude.

 

From this i can conclude that the disk "cloners" such a TI & ghost, copy the volume serial # over to the new HDD, my process with disk director did not. That can be dangerous if you leave both HDDs in the system, but most folks don't do that.

 

I am setting up my original Hitachi with Acronsi TI and will try to use that for XP cloning.

 

I need to be able to clone to a smaller drive as well as a bigger drive - that's why is was using Disk director.

 

Worth noting that EMC9 was the ONLY major app that will not run on my 'semi-cloned' drive...