Results 1 to 9 of 9
  1. #1
    New Lounger
    Join Date
    Dec 2009
    Location
    Chicago, IL
    Posts
    24
    Thanks
    8
    Thanked 0 Times in 0 Posts

    Trying to Fix MSVCRT.dll file errors (XP Pro sp3)

    I have been experiencing problems with an application that uses MS office (especially Access) for underlying database work on my XP Pro machine since last spring. The developer says the problem relates to a bad MSVCRT.dll file needed to handle their program’s C++ code, and a simple re-registering / removing excess copies should take care of the problem running regsvr32.exe .... but that results in an error message “msvcrt.dll was loaded but the DLLRegisterServer entry point was not found. The file can not be registerted.

    After checking an old Fred Langa article in WS about another user’s problem (with a different *.dll file) he seems to make a generalized statement that to fix this problem e.g., Use a search tool to scour your system for any instances of dllfile.dll. Normally, you should have only one copy in the WindowsSystem32 folder. Delete or rename any other copies (for example, as dllfile32.old or .bak). Check each copy’s properties, such as version number and creation date, etc.

    This is similar advice I was given my the application developer but when I do this I find multiple copies in different windows directories (besides system32, e.g., \windows\system32\dllcache and also copies in the reinstalled c\program files\java\jre6\bin directory and also in the program files for the nero7 cd program.

    What I first thought was the problem is that when checking the properties for msvcrt.dll file in the main system32 directory (c:\windows\system32) it is described as “Windows NT CRT DLL” (File version 7.0.2600.5512 ) vs. the version and description for the msvcrt.dll file in the recently re-installed java directory c\program files\java\jre6\bin directory is seemingly correctly called “Miscrosoft ® C Runtime Library” (version 6.0.8337.0) leading my amateur mind to think the dll file in the java directory is the correct one. This msvcrt.dll file also seems to be the same or similar to the v6.0.8797.0 found in the C+++ runtime components file discussed here : http://support.microsoft.com/kb/259403

    But when I do rename the file e.g. msvcrt.old -- a new copy is automatically created that is identical to the one renamed, and if I try copying the hopefully correct one from the java directory, it the file in the system32 directory automatically is changed back to the previous version. Could this be related to a file called msvcr40.dll file that has as its description “VC 4.x CRT DLL (Forwarded to msvcrt.dll)” and btw has the same date as the troubled msvcrt.dll file? Also in the system32 direcotry there is a file called msvcr20.dll dated 2001 that shows the same name as what it seems it should be, ie “MS C Runtime Library”

    Sorry for the long post but since I am not really technically qualified to be digging around the windows/system32 directory, I don’t know how else to explain the problem and what I have tried ... thanks in advance for any thoughts or ideas.

    TGH

    Ps – I also found this this article on “how to fix msvcrt.dll errors” ( http://www.instant-registry-fixes.or...crtdll-errors/ ) and wondering if this is a reputable site and accurate information? My main concern is that since I did a complete reinstall of my XP Pro system this summer and the problem msvcrt.dll problem persists, I would just wind up copying from the XP Pro install disk the same file I have now. Then again, when I did a complete reinstall a year ago due to a virus episode, everything worked fine (until last May).

  2. Subscribe to our Windows Secrets Newsletter - It's Free!

    Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!

    Excel 2013: The Missing Manual

    + Get this BONUS — free!

    Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!

  3. #2
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    A bit of hunting around suggests that the version you have is a newer updated C++ runtime library - but I'm not 100% sure about that.

    Given the rather odd behaviour you note, it can't hurt to run some intensive scans for rootkits etc, just in case.

    Another line to follow up, (conditional on there being no similar errors when using other applications written in Visual C++) is to challenge the assertion from the developer that the dll is somehow "bad".

    Ask then to explain exactly what they mean by that and describe why it should fail with their code and not with other applications - assuming that to be the case of course! Some developers may be in the habit of hiding flaky code by blaming dynamically linked libraries - a good developer will engage with you to give a solid base for their assertion, which will give you much more confidence.

    Looking at the instant registry fixes site, it appears legitimate and whois suggests it's been running for a couple of years. I am however rather skeptical of a site that brands itself in such terms, but that may just be me being paranoid. If you have an installation disk, you can extract (using the expand command) the original dll using the recovery console. Boot off the CD to be sure you are working with clean files.

  4. The Following User Says Thank You to Tinto Tech For This Useful Post:

    TerryGH (2011-11-05)

  5. #3
    New Lounger
    Join Date
    Dec 2009
    Location
    Chicago, IL
    Posts
    24
    Thanks
    8
    Thanked 0 Times in 0 Posts
    Thanks for the reply, Tinto .... Can you clarify what you mean by "odd behaviour" e.g., are you referring to the initial error message when trying to register the msvcrt.dll file or that I am unable to copy another file version over the one in the windows\system32 directory? And are you saying your research shows the msvcrt.dll version (“Windows NT CRT DLL” (File version 7.0.2600.5512 ) ) is the correct file vs. the msvcrt.dll versions used by java?

    On potential malware/rootkit I have started another update run for Malwarebytes tonight but between it, MSE and just this week the MS security tech running ComboFix on my pc regarding an office update issue -- so far it does not look like a virus type issue.

    Regarding the developer's program reliability -- I have been running this stock market modeling/charting program (AIQ TradingExpertPro (TEP)) since 2005 without any problems at all one 3 different XP machines and the message when TEP crashes is similar to the run that I get when I run regsvr32.exe ala "....entry point was not found" the application error is something like "the instruction at "0x73dd11a3" referenced memoray at "o.o etc) . the memory could not be read" -- not sure if that means anything but the error specifically mentions the name and version of the msvcrt.dll file.

    Anyway, thanks again -- assuming the malwarebytes scan returns clean as expected -- do you think the next best attempt is to retrieve/expand the original dll via the recovery console? TGH

  6. #4
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    Can you clarify what you mean by "odd behaviour" e.g., are you referring to the initial error message when trying to register the msvcrt.dll file or that I am unable to copy another file version over the one in the windows\system32 directory? And are you saying your research shows the msvcrt.dll version (“Windows NT CRT DLL” (File version 7.0.2600.5512 ) ) is the correct file vs. the msvcrt.dll versions used by java?
    Both really. It seems odd that when you replace v7.0.2600.5512 manually with a v6.0.8797.0 from the Java Runtime library the v7.0.2600.5512 reappears in place, but that may be due to the behaviour of the msvcrt40.dll which specifically notes Forwarded to msvcrt.dll - I don't know enough about that to be certain.

    Also the I found references to both versions of the file while googling around. One an XP Home system here, I have msvcrt.dll at v7.0.2600.5512 as you do, but I also have a msvcrt40.dll at v5..0.2600.551 which says VC 4.x CRT DLL (Forwarded to msvcrt.dll).

    Now, something that concerns me a bit: I'm curious about why a Microsoft tech security guy would run ComboFix on your machine - that application is designed to search for and remove specific malware. Have you been seeing any other indications of malware issues?

    A rhetorical question - What was the issue with Office Updates and why did the tech security guy suggest running ComboFix for an updates problem? A red herring perhaps, but one that throws an extra variable into the mix for sure.

    Did you contact MS yourself, or the other way round?

    If you have seen malware issues and you have a file that is doing strange things, you could also run scans for rootkits - try the Kaspersky TDSS Killer and the Sophos Anti-rootkit scanner.

    I hear what you say about the TEP application reliability. My comment was an observation on "the dll is bad" reply from the developer: that it seemed to be a bit of a fob-off. However, since it appears to be a stable application and you have seen no issues on other machines, that may be a blind alley.

    If all the scans come up clean, yes, you could try the expand from the install disk, but consider extracting both the msvcrtdll and msvcrt40.dll files since they seem to be a bit intertwined.

  7. #5
    New Lounger
    Join Date
    Dec 2009
    Location
    Chicago, IL
    Posts
    24
    Thanks
    8
    Thanked 0 Times in 0 Posts
    Well back after trying to be productive on other tasks today, but did get the malwarebytes, Sophos and TDSS killer scans run and all came up clean. A tech friend had also suggested running GMER which I did and sent off the log report to them for review. At this stage I actually was kind of hoping to have found some type of malware problem since no one yet can explain why which version of the msvcrt.dll file I should have -- not to mention the strange behavior of not being able to copy the java version 6x to the system32 directory.

    And yes, I initiated the call to the MS tech security guys at their free "pc-safety #(866-727-2338) since I could not get 3 Office 2003 updates from September to install -- after being passed onto the "level 2" tech guy and his remote efforts to get things to work he said some office files had been corrupted and office reinstall would be needed except he did not recommend I do that unless I was prepared to reinstall XP Pro again. The strange thing is that I make extensive use of Excel/Access and Outlook and have not had any problems at all -- except for this update problem and the TEP application mentioned above.

    I am out of time for now to try the "boot to XP install CD/expand both dll files" process but it would seem to me if I can't complete a simple copy and paste of the java version 6x of the "problem" msvcrt.dll v7x -- wouldn't I likely have the same problem expanding/copying the files from the XP install disk?

    Just one last question -- can you or someone think of how I can find our for sure which version of the msvcrt.dll file I should have and if the inablity to copy a replacement file is "normal" behavior for this file? Once again Tinto -- thanks for you help.

  8. #6
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    Well, it's good that you called MS tech support - there are stories (and a thread here in the Lounge) about cold calling from MS tech support that are scams.

    Regarding running ComboFix for an Office Updates problem: I'm still unsure why the MS Tech guy thought that should have been necessary.

    I can confirm on an XP system here the msvcrt.dll file is at version 7.0.2600.5512, but I don't understand the link between the msvcrt40.dll (which in it's description says "Forwarded to msvcrt.dll") and the msvcrt.dll itself. Maybe another Lounger here might have an idea about that.

    I think at this stage, there is no harm to try expand both files after booting from an installation disk. If booted off the installation disk, replacing both files in one session may overcome any corruption or masking behaviour in the OS. However, also consider the advice from the MS Tech Support guy. It's difficult to blindly agree with that from a distance without knowing exactly what it is he found and why he recommended a re-install of Office and the OS itself, but like a sledgehammer to crack a nut - it should resolve the issue.

  9. #7
    New Lounger
    Join Date
    Dec 2009
    Location
    Chicago, IL
    Posts
    24
    Thanks
    8
    Thanked 0 Times in 0 Posts
    ahhh I too had heard about such scams and never realized MS boys would have any free type of support especally for XP these days so had double confirmed the pc-safety # before calling. Anyway re your Combofix question -- all I know is that the Level 2 tech had tried all the "normal" remote taks to try to fix the office update problem, and combofix was the last thing he tried to get an "answer" to the problem -- but as mentioned combofix and its 50? tests/passes came out ok showing now malware.

    I still need to get the time to do the install disk boot/expand etc and obviously hoping to avoid restoring XP again -- especially since the XP OS reinstall in August didn't fix this msvcrt.dll problem. I am now just wondering if there a reason I could not try running the regsvr32.exe program on the msvcrt.dll in the java directory? I can always then to the boot to the install CD to get the correct files right? Thanks and my apologies for dragging out what seems like should be a simple problem to fix ...

  10. #8
    Lounge VIP
    Join Date
    Apr 2011
    Location
    Scotland
    Posts
    1,168
    Thanks
    44
    Thanked 134 Times in 115 Posts
    especially since the XP OS reinstall in August didn't fix this msvcrt.dll problem
    I don't think you previously noted that you ran an OS re-install and that it failed to correct the problem. That raises some even more fundamental questions.

    Stepping back for a moment, you have a problem with Office updates and a dll that appears not to link when a developers app that requires Office runs, an intertwined issue with a 2nd dll and some confusion about a 3rd dll in the Java Runtime library. Have you uninstalled Office, cleaned up and then re-install Office? It might help.

    Other than that, perhaps the best option is to take an image backup, copy your user data off to a safe place and run a complete clean install - rather than a non destructive installation - then re-load Office etc and copy your data back in. In other words start from a clean slate.

    Perhaps others here may have some ideas?

  11. #9
    New Lounger
    Join Date
    Dec 2009
    Location
    Chicago, IL
    Posts
    24
    Thanks
    8
    Thanked 0 Times in 0 Posts
    My apologies if I have wasted time but I thought I had mentioned the complete XP SP2 disk reinstall but re-reading my notes obviously not -- btw, the August reinstall was after complete data backup and reformatting the SATA HD, updating as needed and obviously a fresh reinstall of Office. But that is what is so frustrating with just this relatively small problem (90% of the TEP application works fine) and the office update problem in September my system is running great. I even ran a check disk on the SATA HD not too long ago and that tested ok.

    Anyway, before I attempt to reinstall Office 2003 I need to be prepared to do another complete XP reinstall so I am still hoping to avoid another week of disruption but if that is what it comes to so be it. I have to run now but once again Tinto I appreciate you help ... just wish there was a simple solution *s

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •