There is no use screwing up your fresh .net/Visual Runtime install by overwriting one of it's dll's by some random internet one xD.
Edit : Anyways, Delete the random MSVCR100.dll from your system files some CA skiddy certainly asked you to install to "fix" one of the bugs his hacks had. (this is an assumption).
Last edited by Melodia; 06-02-2011 at 12:39 PM.
Love You All~
When you reinstalled it, you sure you deleted everything?
uninstall -> reboot -> install -> reboot -> done
Ah we-a blaze the fyah, make it bun dem!
I hate to disagree with you, but it's very possible to screw it up. If the function he is trying to access is in the DLL he overwrote with another one ( assuming its missing this function ) it'll probably give you that error he's shown.
Please take notice of the bolded text. :P
Latest MS crap will have all the functions ?
If Mr. Skiddy compiled using screwed up .Net libraries that requires a screwed up dll this is not really a correct practice to install his one over yours., And even if you do it should be in the application dir and auto-loaded, not sysfiles.
Anyways corrupted files are corrupted, I don't get why people mod .Net libs ; They are already crashy enough alone.
Love You All~