|
|
#1 |
|
Junior Member
Join Date: Jan 2010
Posts: 2
|
WinAmp 5.572 Fails to Start After Upgrade
I've been using WinAmp without problems for YEARS! Today I downloaded 5.572, and it won't run.
The attached pic shows what I've downloaded, the display from Control Panel -Add & Remove Software showing that it is installed, and the error message saying that MSVCR90.dll is missing. I've done the download and install twice with the same result. WinAmp won't run from either the desktop shortcut, the QuickLaunch bar or Start-Programs. Where to now? |
|
|
|
|
|
#2 |
|
Techorator
Winamp Team Join Date: Jun 2000
Posts: 35,128
|
Hmm, strange...
Info required <-- click! WinXP, yes? Is it sp3? Please attach a List of Plugins via the standalone app. What security/av software is running? (a HijackThis log will show us this, and more) Does the following folder & files exist? %ProgramFiles%\Winamp\Microsoft.VC90.CRT\msvcr90.dll & Microsoft.VC90.CRT.manifest Does installing the Microsoft Visual C++ 2008 SP1 Redistributable fix the problem? |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Jan 2010
Posts: 1
|
same problem here
I have the same problem. I installed Winamp pro with XP.
I was able to plac .Flac files with no problem previously and now the program drives my CPU usage to 100%. The only way I can terminate the program is to stop the process with task manager. Mike |
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Jan 2010
Posts: 2
|
I'm running McAfee as supplied by Comcast.
%ProgramFiles%\Winamp\Microsoft.VC90.CRT\msvcr90.dll & Microsoft.VC90.CRT.manifest exist. installing the Microsoft Visual C++ 2008 SP1 Redistributable fix the problem? NO. I installed it and rebooted. The problem still exists. |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Jan 2010
Location: Maine
Posts: 2
|
This is my first post (and it took 7 tries to create an account... whew)
While fairly new to WinAmp, I've been a programmer and troubleshooter for 25 years. That being said... Given the description you presented the first things I would try is: a. Scan the entire hard drive for a duplicate instance of the DLL(s); you may have two or more copies with different versions. b. Once in a blue moon XP Theme settings can throw a monkey wrench, and c. It never hurts to run "Chkdsk C: /f" and reboot. Good Luck |
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Jan 2010
Location: Maine
Posts: 2
|
Update
I had some spare time, so....
I checked 'winamp.exe' with a dependency checker which shows all calls from one file to all others it touches. It declared that the msvcr90.dll could not be found either, but I am not getting any application errors. It does indeed exist in a winamp subfolder. If I was experiencing your problems I would try disabling all XP theme settings (and reboot), and if that doesn't work try disabling everything non-essential running on your machine which might show some positive results. First and foremost I would set the XP desktop theme to the plain-jane 'Windows XP' style. I've seen this fix a lot of other issues. |
|
|
|
|
|
#7 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
I have the exact same problem. And I'm not alone: http://blog.winamp.com/2009/12/17/wi...now-available/
I have Windows XP SP3. Installing Microsoft Visual C++ 2008 SP1 Redistributable has no effect. Renaming the Plugins folder has no effect either. I can also confirm that both files are installed correctly: C:\Program Files\Winamp\Microsoft.VC90.CRT\msvcr90.dll C:\Program Files\Winamp\Microsoft.VC90.CRT\Microsoft.VC90.CRT.manifest I also checked using Process Monitor in order to determine where Winamp attempts to locate the file. Here are the results: code: In other words, Winamp checks pretty much everywhere except at the right place. I tried copying both files directly in C:\Program Files\Winamp but when I do that I get a 0xc0000142 initialization error instead. >_< |
|
|
|
|
|
#8 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,233
|
loading of the dll is down to the OS so somehow it's not taking into account what the manifest file specifies and so starts looking through the system search path (which is what that output looks like).
however there has only been a few reports of it not working correctly which would point to something else on the installed system - maybe an antivirus app or something like that - preventing the Microsoft.VC90.CRT folder from being recognised as i'm sure there's a way to load a dll with a different search path which causes such as what was seen with the loading of the older nscrt.dll (precursor to the vc9 dll) by some AV apps - which led to having to have the dll also duplicated in the plug-ins folder. either way i'm now getting out of my depth as the whole SxS stuff confuses me at this time of night. -daz |
|
|
|
|
|
#9 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
Personally I'm using AVG Free as my antivirus software.
Also, I always do a custom install when upgrading Winamp because I don't like having Winamp Library installed. Still, I don't see how it could cause this issue. Yet another possibility is that I am using a French version of Windows. I would be very surprised, but maybe it's one of those things? In the meantime, is it possible to have a download link for version 5.56? |
|
|
|
|
|
#10 |
|
Techorator
Winamp Team Join Date: Jun 2000
Posts: 35,128
|
The plot thickens.... Confirm that you're not running Winamp in compatibility mode (winamp.exe -> Properties -> Compatibility tab: Everything should be unchecked) Please also zip up & attach the two logs I asked for in my first reply (standalone "List of Plugins" & HijackThis logs) Old unsupported versions can be found here: http://www.filehippo.com/download_winamp/ http://www.oldversion.com/program.php?n=winamp |
|
|
|
|
|
#11 |
|
Junior Member
Join Date: Feb 2010
Posts: 2
|
Same problem here, last month updated to 5572 and bango it crashes on load. got pissed off and stopped using Winamp but tonight after missing the convenience of the 'Amp' decided to have another go, so re-downloaded 5572 and CRASH down it goes in flames!!
So tuned into this forum to find others same problemo!! Read the post about Plug-ins - although I'm only using the Messenger plugin I deleted all the files from the plug-in folder and whatchya know! Winamp! up and old sk00l on me desky!... so while Winamp was running as Agent in task bar dropped all the files back in and double clicked the agent and presto skinned Winamp! playing in all its Ampy glory... Havn't re-started me compy yetsky... Havn't looked at which Plugy is doing the dirty on me Ampy... All to report so far... |
|
|
|
|
|
#12 |
|
Techorator
Winamp Team Join Date: Jun 2000
Posts: 35,128
|
Messenger plugin... as in... gen_msn7.dll?
If yes, then I've already added that thing to the auto disable section of the installer for the next release: http://forums.winamp.com/showthread.php?threadid=316088 |
|
|
|
|
|
#13 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
Lucky for you MrJackson. Unfortunately that doesn't work for me - even when the Plugins directory is empty Winamp still crashes. Also, I don't have any gen_msn7.dll or any Messenger plugin that I could think of.
I included the HighJackThis log and the plugins list as requested in the ZIP file. Note that the error message was displayed during the HighJackThis scan. Also, when I ran nunz.exe to scan for plugins, I again got the MSVCR90.dll error right away, but thankfully the text files were still generated while the error message was displayed. I also followed the tip generated by nunz.exe and opened winamp.exe with Dependency Walker, and even the tool cannot find MSVCR90.dll. Not only winamp.exe directly depends on it but also nsutil.dll, tataki.dll and zlib.dll. I also opened all DLL files located in the root directory manually and discovered that libflac.dll, libmp4v2.dll, libsndfile.dll and nde.dll are also dependent on that file. Hope this helps! |
|
|
|
|
|
#14 |
|
Techorator
Winamp Team Join Date: Jun 2000
Posts: 35,128
|
@SmashManiac
Hmm, so you can confirm that winamp.exe definitely isn't being run in Compatibility mode then? (see my previous post) All of the default system components (Winamp\System\*.w5s) and nearly all of the DLLs (Winamp & Winamp\Plugins folder) are msvcr90.dll-dependent (except for gen_jumpex, dsp_sps & vis_avs). Notice how your my_plugin_list_ext.txt says "Loading test failed" next to almost everything. All your 3rd-party plugins seem to be loading ok, though I'm not sure if one or more of these are to blame for the overall problem... gen_sripper.dll in_CDReader.dll in_APE.dll dsp_pacemaker.dll out_HQSP_Resampling.dll out_volumelogic.dll out_filewrite.dll I recommend that you disable all of these for now (move them into some backup folder somewhere else) The log seems to suggest that these 3 files in the Winamp root dir could hold the key... burnlib.dll primosdk.DLL lame_enc.dll All 3 of those are listed as "loaded" lame_enc.dll is from some 3rd-party plugin, maybe streamripper. Winamp also installs a lame_enc.dll in the Plugins dir, alongside enc_lame.dll but only if the MP3 Encoder is checkmarked in the installer options (your plugin list shows no encoder plugins are present) burnlib.dll is installed alongside the Rip & Burn media library plugin primosdk.dll is installed alongside the Sonic Burning Engine. burnlib.dll will be loaded by winamp.exe, but might cause winamp.exe not to load properly if an old version of burnlib.dll is present... I assume you unchecked these items in the installer options but the old dll's from a previous installation are still present. Did you try a clean install yet? http://forums.winamp.com/showthread....d=161361#clean Other than that, if it still fails, then try adding winamp.exe to the Exclusion List in AVG. Something seems to be altering the loading path of dll's on your system. WinXP and higher support side-by-side assembly (ie. placing dependencies such as msvcr90.dll in subfolders), but Win2k and older don't (the dependency needed to be in the same folder as the exe or in %system% dir on Win2k) So basically, it looks like something is messing with that loading structure on your system.... (which is why I asked about compatibility mode, ie. if Winamp is being run in Win2k or earlier mode). [EDIT] And hmm, any idea what this item is in your HJT log? O4 - HKCU\..\Policies\Explorer\Run: [{3B1508EA-0AE9-3084-0525-050112050002}] "C:\Program Files\Fichiers communs\{3B1508EA-0AE9-3084-0525-050112050002}\Update.exe" mc-110-12-0000272 |
|
|
|
|
|
#15 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,233
|
burnlib.dll is unlikely to be it as that's a resource only dll with no dll load dependencies.
however, with the talk of dll dependencies, SmashManiac can you see if dependency walker will load MSVCR90.DLL (should only be dependant upon KERNEL32.DLL) - just trying to think of what can be checked to rule out options. the other thing would be to see what happens if AVG is completely disabled (if it can be) as i'm really starting to wonder if that is somehow altering the dll loading search path. -daz |
|
|
|
|
|
#16 |
|
Junior Member
Join Date: Feb 2010
Posts: 2
|
Back with a new XP boot-up in the morning...
first thing I notice is Ampy Agent gleaming at me from Tasky as it was before but this time double clicked to find Ampy up and shiny on me desky, and not "error failed to load appy"... gen_msn7.dll is the plug-in and its back in and working... checked the various skins on the Ampy and all seems OK!... So I went from not being able to start Ampy to running it like nothing happened and all is forgiven kissy kissy... What was that about WinAmpy? you went drama queen pshyclo for a monthy
|
|
|
|
|
|
#17 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
@DJ Egg
Yes, I can confirm that Winamp is not running in Compatibility Mode. Sorry I forgot to mention that in my previous post. I also tried adding the Winamp directory in the exclusion list of AVG but nothing different happenned. To verify I moved the 3 DLLs you mentionned as suspicious and I still had the same crash. As for lame_enc.dll, I actually put it there manually. It comes from Audacity. I also checked what was the "Update.exe" entry... and the {3B1508EA-0AE9-3084-0525-050112050002} directory was empty. Guess it was just a leftover entry in the registry. In any case I deleted the directory and will clean the registry soon of that entry (I need to do a major cleanup of startup programs). I'm surprised about burnlib.dll and primosdk.DLL because they shouldn't be there at all based on your comments. I'll try doing a clean install soon and I'll post the results. @DrO I was able to load MSVCR90.dll in Dependency Walker (and indeed it is only dependent to kernel32.dll). As for AVG, the only way to completely disable it is to uninstall it. I might try it as a last resort if all else fails. |
|
|
|
|
|
#18 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
OK so I uninstalled Winamp and all of my plugins, and then I deleted what was remaining in the Winamp directory. After a clean install, I am happy to report that IT FINALLY WORKS!
However that didn't explained why it wasn't working before, so I opened winamp.exe with Dependency Walker, and guess what? MSVCR90.DLL is now detected correctly! I then opened the Winamp directory in order to understand what was happening and then it struck me. There was a major difference, and it explains everything: THE FILE WINAMP.EXE.MANIFEST NO LONGER EXISTS IN WINAMP 5.572! Directly upgrading Winamp does not remove old files but rather overwrites them. This usually results in no trouble because obsolete files are simply not used by the updated application. However, manifest files are actually used by the operating system, so the previous reasoning does not apply. I believe this is what caused the MSVCR90.DLL crash. Can somebody else verify if deleting winamp.exe.manifest indeed fixes the problem in order to confirm my theory?
|
|
|
|
|
|
#19 |
|
Junior Member
Join Date: May 2008
Posts: 3
|
It works
I can confirm that deleting the winamp.exe.manifest file fixed the problem I was having with MSVCR90.dll being reported missing.
|
|
|
|
|
|
#20 |
|
Techorator
Winamp Team Join Date: Jun 2000
Posts: 35,128
|
D'oh!
Wow, afaik, we haven't used an external winamp.exe.manifest file for ages, maybe not since pre-5.1x days. The manifest has been embedded inside winamp.exe for at least the past 5+ years. So yup, that would explain it... I'll add it to the list of files to remove by the installer for the next release. Thanks, and hallelujah! |
|
|
|
|
|
#21 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,233
|
well that all makes sense then with the OS will use the external file instead of the built-in manifest file and explains why the msvc directory wasn't being included in the search path as it was being told to effectively ignore it (oh how i love those manifest files, heh).
-daz |
|
|
|
|
|
#22 |
|
Junior Member
Join Date: Aug 2005
Posts: 6
|
w00t, glad to help!
|
|
|
|
|
|
#23 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,233
|
i think it's more that we're just glad to have finally worked it out incase it manifests (no pun intended) itself on other client installs.
-daz |
|
|
|
|
|
#24 |
|
Junior Member
Join Date: Feb 2010
Location: California
Posts: 2
|
Still have MSVCR90.dll error.
Hold on one moment.
I installed Winamp 5.552 on a new XP sp3 install. I get the now famous MSVCR90.dll message. I have no winamp.exe.manifest file on the system. If I click through the error messages my Winamp will come up and work, but the message are very annoying. I also have no antivirus program installed at this time. I do not see this problem as fixed at this time. |
|
|
|
|
|
#26 |
|
Junior Member
Join Date: Feb 2010
Location: California
Posts: 2
|
Yes I said 5.552 failed.
I read throught the entire thread and saw that 5.56 worked so I tried 5.552 which I had running on another pc with XP sp2 with no problem. Well 5.552 did not work on XP sp3. I got the error message about the ddl.
I went and got 5.572 to give it a shot and low and behold it loaded and is working just fine. I guess the problem is fixed in 5.572. Eureka !! Thanks guys.
|
|
|
|
|
|
#27 |
|
Junior Member
Join Date: Aug 2007
Posts: 2
|
I had the same MSVCR90.dll missing error.
Fix: go to C:\Program Files\Winamp delete WINAMP.EXE.MANIFEST Start winamp done Thanks for the help peopleMaybe we should update more often... lol |
|
|
|
|
|
#28 |
|
Member
Join Date: Aug 2004
Location: downstairs
Posts: 92
|
Ah! Solutions can be so easy as deleting one file. Finally I could update from 5.56 to the current 5.572.
Thanks everybody |
|
|
|
|
|
#29 |
|
Junior Member
Join Date: Jun 2010
Posts: 1
|
Thanks a lot, that helped
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|