The product appears to be validated, but machine SID doesn't match. Delete file C and re-activate.

Boy, what a great descriptive help box that popped up!  What the h3!! is "file C" and "re-activate" what????

I've only installed this once on this same PC (laptop).  However, over time this laptop has become semi-obsolete and I've had to wipe and re-install windows (same version/disk) using the manufacturer's (HP) restore system disk.  I assume that by restoring the system, I somehow changed the SID (whatever that is) so while the product recognizes the game file as legitimate (not a thief, thank you) it won't let me play.

 

What kind of crap is this???  I am NEVER EVER EVER EVER going to buy a game by digital download only.  Sure would like to play!!!!  Second DD game now that I've wanted to go back and play after a lengthy time away only to have issues.  Convenience of digital download... my hooo-hah!

Thanks for any advice!

 

 

 

4,298 views 5 replies
Reply #1 Top

Well, considering Impulse will let you put it on any believable number of computers, I don't know why its giving you issues. I would try manually deleting everything in the SoaSE folder and reinstall it (assuming you've tried the uninstaller already).

Reply #3 Top

I have the same error.  I briefly swapped motherboards due to attempting a motherboard upgrade, but I the new mobo was DOA so I had to RMA it.  I re-installed the old motherboard and the next time I attempted to play Rebellion I got the exact same error as you.

Googling the error online I don't see any mention of it so I don't think it is a common Steam error, I have no idea what is causing it.  Completely deleting the game client and re-installing it doesn't seem to fix it, neither does re-activating it.

Reply #4 Top

Delete the bin file(s) from C:\Users\All Users\Ironclad Games\Sins of a Solar Empire\License, then run the game and reactivate. Activations are specific to particular Windows installations.

Reply #5 Top

Thanks for the response, kryo, I will attempt that this evening and let you know the results.

I did run "sysprep" on my system prior to the planned motherboard upgrade so I had to re-activate windows even after re-installing the original motherboard.  It makes sense that I would have to re-activate other software as well, it's just frustrating to get such an unhelpful error message.

 

EDIT:  I can confirm that this fixed my problem.  Though the file path kryo listed wasn't exactly accurate for my PC, but I was able to search to find the necessary .bin file.