I have seen a couple of XP SP3 systems in our company which have a modified runtime library "msvcr71.dll" in their c:\windows\system32, differing from the dll delivered with a fresh XP installation.
As a result the SAP setup for example fails because it detects the file to differ in size, tries to replace it and fails because it is in use.
|State||Version||Description||Size||Modification date||Digital Signature|
|original||7.10.3052.4||Microsoft C Runtime Library||348160 Bytes||21.02.2003||no digital signature|
|modified||7.10.3052.4||Microsoft C Runtime Library||353680 Bytes||06.06.2011||Adobe Systems, Incorporated (Issued by VeriSign Class 3 Code Signing 2009-2 CA)|
I have seen that modified DLLs with various sizes are bundled with programs like Acrobat 10.0 or Dreamweaver CS5. But in those cases, the files are always located in the program's corresponing installation folder and have a digital signature by Adobe/Verisign. While a modified DLL in a program directory is fine with me I wonder if it really was intentional to modify the dll in the "c:\windows\system32\" folder.
Unfortunately I could not pinpoint the issue to the installation of a certain Adobe product.
Has anybody else experienced this issue?
Adobe Reader and Acrobat does not modify "msvcr71.dll".
I am not sure about other Adobe products, if they modify this file or not. You can confirm it from other Adobe products' user forums (like Dreamweaver or any other product which is installed on your machines where the issue is found.)
You can find a link for Adobe's other user forums at http://forums.adobe.com/index.jspa .