this error occurs at the login screen. shortly after entering password, and hitting enter. game worked prepatch. 3.2 microsoft visual C++ runtime library Runtime error! Program c:\program files\world of warcraft\wow.exe R6034 An Application has made an attempt to load the C runtime library incorrectly. Please contact the applications support team for more information. thanks
Same issue here. Any fix?
A user on the Blizzard forums fixed the issue by downloading and running the installer for Visual C++ 2005 sp1 redistributable (not from winetricks but manually): http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=200b2fd9-ae1a-4a14-984d-389c36f85647&displayLang=en Worked for me as well. Awesome!
ok anyone froze at the waiting screen ? I chose a character and clicked enter now I am stuck there grr and can't close out of wow, any ideas if this is a result of the new patch ? thanks in advance.
Yeah, seems to be even rougher than usual tonight. :P My partner's game crashed, and it wouldn't let him back onto the realm; I logged out to do some real-life things with him, and now I can't even connect to the authentication server anymore, seems to be down. Seems like a good night to put a movie in and ignore WoW while they sort it all out!
Hey I have been having the same issue all morning. I tried both fixes listed above and I am still getting the same error :( Anyone else having the same issue after trying both of the fixes posted above?
microsoft c++ update posted above fixed it for me too, thanks!
still getting error also
microsoft c++ update posted above fixed it for me too, thanks!
C++ update worked for me.
death wrote:> any ideas, why i am still gettin this error when, i have installed C++update from microsofts site, still getting errorMe too. Do any of the C runtime libs have to be set as overrides for native vs built-in?
microsoft c++ update posted above fixed it for me too! Thanks so much for this fix! :)
The manual install worked just fine of the 2005 lib.
PiperMatt wrote:> This has apparently worked for some folks: > > Code: > > wget http://www.kegel.com/wine/winetricks > sh winetricks vcrun2005sp1 vcrun2005 > > >Worked for me, thanks!
BTW i got everything working by removing all x86_64 wine rpms (just leave the i386 or i586 rpms), and then installing the C++ executable So if you are running x86_64, try that as a fix
All my folder permissions on that drive are RW for users and root. And I run WoW in user mode, not root. I have tried running it in both, but I still get the same issues in Root. Is that what you meant by folder permissions? RW access?
Yea, what is the exact error/problem? On Wed, Dec 9, 2009 at 11:11 PM, Fallhallen <wineforum-user at winehq.org>wrote:> All my folder permissions on that drive are RW for users and root. And I > run WoW in user mode, not root. I have tried running it in both, but I > still get the same issues in Root. Is that what you meant by folder > permissions? RW access? > > > > > >-- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20091209/72a3a17a/attachment.htm>
Same error everyone else is getting: microsoft visual C++ runtime library Runtime error! Program z:/mnt/Windoze/Users/Games/world of warcraft/wow.exe R6034 An Application has made an attempt to load the C runtime library incorrectly. Please contact the applications support team for more information. The error appears after you enter your username and password and click the login button.
On Wed, 09 Dec 2009, "Fallhallen" wrote:> For those who have successfully fixed this issue, What type of install > are you guys using? Did you install WoW in Wine? Or are you pointing to > a WoW installation on a Windoze drive? > > I am using Slackware 13 and wine-1.1.23A fellow slacker!! :-) As a data-point, I'm running Slackware 11 and wine-1.1.34 (self built).> I have a duel-boot on this machine, running Windoze 7 on a separate HD. > I run WoW in linux by simply pointing to the WoW executable in my Windoze > drive. I have never had a problem before this update. I have tried using > Winetricks to install the aforementioned upgrades, that did not work. I > also tried downloading the source and running that install as mentioned. > This also did not work. I am wondering if it is not working because I do > not have a native Wine install of WoW? I could not get WoW to install in > Wine using the DVD's or the Downloader. Is there an easy workaround to > get things back up and running again? Having to reboot multiple times a > day is a pain.I actually took a different approach. I removed the following files from my WorldofWarcraft directory: Microsoft.VC80.CRT.manifest msvcr80.dll It seems these were either incorrectly installed by the patch. Further more, it only placed this one file from the full MSVC Runtime instead the rest of the files which are usually distributed with it. It appears the manifest doesn't match the file (which is why you get the bizarre error message about the runtime being the incorrect version). So, I removed both of them and WoW loaded just fine for me. Go figure. YMMV.> Thanks-- Peter A. Castro <doctor at fruitbat.org> or <Peter.Castro at oracle.com> "Cats are just autistic Dogs" -- Dr. Tony Attwood
hrm.... I had hopes, but that had no effect for me. Same error. Are you running Wine in XP mode? Is there anything I need to change in Winecfg? I have mine set for XP mode.
On Thu, 10 Dec 2009, "Fallhallen" wrote:> hrm.... I had hopes, but that had no effect for me. Same error. Are you > running Wine in XP mode? Is there anything I need to change in Winecfg? I > have mine set for XP mode.I'm running in XP mode, but it doesn't seem to matter (I've tried Win 2000 mode and WoW doesn't seem to care). I didn't change anything in winecfg either. Are you getting the R6034 Runtime error? If so, have you applied the vcrun2005sp1 or vcrun2005 via winetricks? The runtime appears to be under C:/windows/winsxs. In the /manifest dir under winsxs there should be a correct manifest for Microsoft.VC80.CRT.xxxxx. eg: x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700 Check that that matchs the actual directory of the same name under winsxs. Then check that your system.reg has the same references to that same version (there were 8 references of them in mine). I recall the error said what the versions it expected and found. Check that you have that version in the manifest directory. In my example, it wanted "4053" but the installed version was actually "762". The erroneous 4053 was coming from that Microsoft.VC80.CRT.manifest in my WoW directory. Once I removed that, it looked for the manifest in the correct (ie: registered) place. I don't know weither WoW really needs this apparent update (4053) or not. All I know is that my game play doesn't seem to encounter any problems (yet). One additional thing to note. I had trouble applying vcrun2005sp1 via winetricks myself. It starts to apply it and then appears to error out (though I'm not really sure Im reading the output correctly), so I don't really know if I even have vc2005sp1 installed correctly (still have to verify the version numbers somehow). Again, YMMV. Good luck! -- Peter A. Castro <doctor at fruitbat.org> or <Peter.Castro at oracle.com> "Cats are just autistic Dogs" -- Dr. Tony Attwood
I'm not really understanding you... docfruitbat wrote:> > Are you getting the R6034 Runtime error? If so, have you applied the > vcrun2005sp1 or vcrun2005 via winetricks?Yes, I am getting the R6034 Runtime error. Yes I applied both patches via winetricks (I also tried the manual patch as mentioned earlier) docfruitbat wrote:> > The runtime appears to be under C:/windows/winsxs. In the /manifest dir > under winsxs there should be a correct manifest for > Microsoft.VC80.CRT.xxxxx. > eg: > x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700I have a C:\windows\winsxs\manifests directory, which holds over 10,000 files. There are 6 different x86_Microsoft.VC80.CRT files. Most of them are version 762. docfruitbat wrote:> > Check that that matchs the actual directory of the same name under > winsxs. Then check that your system.reg has the same references to that > same version (there were 8 references of them in mine).There are no sub-directories in C:\windows\winsxs\manifests so I cannot match the file with a directory. Also, I do not know where system.reg is located. I did a search, found nothing. Here is what my WINE is telling me: fallhallen at SlackHem:~$ wine /mnt/Windoze/Users/Public/Games/World\ of\ Warcraft/WoW.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WS_setsockopt Unknown level: 0x00000029 fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub fixme:iphlpapi:GetAdaptersAddresses no support for IPv6 addresses fixme:iphlpapi:GetAdaptersAddresses no support for IPv6 addresses fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 fixme:service:EnumServicesStatusW 0x1246c0 type=30 state=3 (nil) 0 0x87e7c8 0x87e7d4 0x87e7d0 fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x20000001,(nil),0x0001,0x00000000,0x87e5d8,(nil)): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x20000001,(nil),0x0001,0x00000000,0x1244f0,(nil)): stub fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762) fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling mixer fixme:advapi:SetSecurityInfo stub archive Data\enGB\patch-enGB.MPQ opened archive Data\patch.MPQ opened archive Data\enGB\patch-enGB-2.MPQ opened archive Data\patch-2.MPQ opened archive Data\expansion.MPQ opened archive Data\common.MPQ opened archive Data\common-2.MPQ opened archive Data\enGB\locale-enGB.MPQ opened archive Data\enGB\speech-enGB.MPQ opened archive Data\enGB\expansion-locale-enGB.MPQ opened archive Data\enGB\expansion-speech-enGB.MPQ opened fixme:win:EnumDisplayDevicesW ((null),0,0x39ed9c,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39ebd4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f2cc,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f3e0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f578,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f574,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f5e0,0x00000000), stub! fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fixme:win:EnumDisplayDevicesW ((null),0,0x39eff8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39f130,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39dedc,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39df04,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x39ded0,0x00000000), stub! fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 5000 fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 5000 fixme:reg:GetNativeSystemInfo (0x37404484) using GetSystemInfo() fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762) fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762) fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fallhallen at SlackHem:~$ fixme:service:EnumServicesStatusW 0x1246c0 type=30 state=3 (nil) 0 0x87e7b0 0x87e7bc 0x87e7b8 If I am reading this correct, it is looking for a Microsoft.VC80.CRT" (8.0.50727.762) version file. From the aforementioned directory, those numbers match up. So what exactly am I suppose to do? I prefer to have very specific idiot proof answers, because I am not fluent in everything, so please do not assume I know how to do anything. Thanks for the help
I am running Ubuntu 9.10 64 bit kernel 2.6.31-16 wine 1.0.1 and the following fix WORKED. Thank you! Fallhallen wrote:> ***FIXED*** > > ***FIXED*** > > Here is what I did: > > Step one, DO NOT DELETE ANYTHING!!!' > > Step two: Navigate to your World of Warcraft Directory (this will be different depending on your version of Windoze) Mine was found in: > > C:\Users\Public\Games\World of Warcraft > > Step Three: Edit the Microsoft.VC80.CRT.manifest file > > Step Four: Find the line that looks like this: > > <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity> > > Replace the version number to 8.0.50727.762 (it should look like this) > > <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity> > > Step Five: Save the file (it is a good idea to first make a backup file before overwriting) > > All done. Your WoW should work perfectly. (You may also need to apply the aforementioned updates). But this worked for me.
tparker at etherstorm.net
2009-Dec-12 15:59 UTC
[Wine] wow runtime error, new with patch 3.3
On Friday 11 December 2009 4:53:28 pm JaySulli wrote:> Btw: does anyone else have recent patch downloads (the last two aswell as> this one) keep changing the file mode on their drive_c/ProgramFiles/World> of Warcraft directory, locking them out? I have to keep chmod-ing mine > back. Not really a problem because this fixes it, but a bit irritating.Yup, that has been happening for a while. You can also change them back through the graphical interface. If you have to do a re-install of the game before this changes I would recommend leaving the window with the wow folder open in the background so you can easily change permissions - after every single little patch! lol.
Help me. I read this post but I'have this error: diana at diana-laptop:~$ wget http://www.kegel.com/wine/winetricks --2009-12-14 00:00:44-- http://www.kegel.com/wine/winetricks Risoluzione di www.kegel.com... 216.92.86.126 Connessione a www.kegel.com|216.92.86.126|:80... connesso. HTTP richiesta inviata, in attesa di risposta... 200 OK Lunghezza: 126833 (124K) [text/plain] Salvataggio in: "winetricks.2" 100%[======================================>] 126.833 145K/s in 0,9s 2009-12-14 00:00:47 (145 KB/s) - "winetricks.2" salvato [126833/126833] diana at diana-laptop:~$ sh winetricks vcrun2005sp1 vcrun2005 Executing wine /home/diana/.winetrickscache/vcrun2005-ms09-035/vcredist_x86.exe fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP000.TMP\\" 00000000 fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP001.TMP\\" 00000000 fixme:advapi:LookupAccountNameW (null) L"diana" (nil) 0x33f854 (nil) 0x33f858 0x33f84c - stub fixme:advapi:LookupAccountNameW (null) L"diana" 0x12af48 0x33f854 0x12f648 0x33f858 0x33f84c - stub fixme:msi:ACTION_HandleStandardAction unhandled standard action L"SetODBCFolders" fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts -> 1 ignored L"Upgrade" table values fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10 ignored L"MsiAssembly" table values err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly Install of vcrun2005sp1 done Executing wine /home/diana/.winetrickscache/vcrun2005-ms09-035/vcredist_x86.exe fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP000.TMP\\" 00000000 fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP001.TMP\\" 00000000 fixme:advapi:LookupAccountNameW (null) L"diana" (nil) 0x33f854 (nil) 0x33f858 0x33f84c - stub fixme:advapi:LookupAccountNameW (null) L"diana" 0x12af48 0x33f854 0x12f648 0x33f858 0x33f84c - stub fixme:msi:ACTION_HandleStandardAction unhandled standard action L"SetODBCFolders" fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts -> 1 ignored L"Upgrade" table values fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies -> 10 ignored L"MsiAssembly" table values err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly err:msi:ITERATE_PublishAssembly Component not set for install, not publishing assembly Install of vcrun2005 done winetricks done. I'm play wow with CrossOver. Can you help me!
Hey guys, So I installed WoW by copying and pasting my brother's Windows WoW install into my .wine Programs folder. I got it all working after a few hours of tweaking without pulling too many teeth. However, there has consistently been this strange 'void' or shadow under all the characters (even the quest givers, vendors, etc.). Look at the pictures - [Image: http://i145.photobucket.com/albums/r204/vestyjr/WoW4.png ] [Image: http://i145.photobucket.com/albums/r204/vestyjr/WoW3.png ] [Image: http://i145.photobucket.com/albums/r204/vestyjr/WoW2.png ] [Image: http://i145.photobucket.com/albums/r204/vestyjr/WoW1.png ] I've given you my video settings as well so you can see how I've set them up. Also, I tried to install the latest AMD Catalyst through my Package Manager (it was recommended on the WineHQ WoW installation and tweaking guide) but it seems to have royally screwed something up - now my FPS rate is at around 1 or 2 while before it was at 10. 10 FPS meant the game was playable... Now, well; not so much. I've followed loads of advice online, but you guys seem to have your shit together. Thanks.
Could be a bug in the video drivers as you're using an ATI card. In any case, if the game is still playable besides those graphical glitches, it's probably a bit lower priority to fix. Still, it'd be helpful if you posted terminal output while running the game. It might indicate any graphics-related stubs, warnings or or fixme's related to the graphical problems.
Okay, so I fixed my FPS problem by doing this - Code: sudo apt-get remove xorg-driver-fglrx sudo reboot I also installed lots things from the Package Manager to do with the Intel chipsets - I have GM965/GL960. So that may have helped..?
henrygrik wrote:> Hi, > Where we people can get the solution of this patch. Please try to release another patch which is better than this one.The solution has been mentioned many times in this topic. And Blizzard in no way will release another patch due to problems people are facing under Linux with Wine. No where in the documentation that is presented by Blizzard does it state that this game is meant to run in anything other than Microsoft. Anytime a patch comes out, it is a standard anticipation by the Linux crowd to expect certain challenges to overcome in getting things working the way they were when it pertains to software that was written explicitly for Microsoft Windows. There are no guarantees this product will work, or continue to work in the future, on anything other than released in the minimum requirements section laid out by Blizzard. If you are unable to get thing working under Linux you have no argument against Blizzard for they never once said this product was meant to run under Linux. We all hope it will continue in the future to be able to run under Linux with the use of Wine. Because we do not want to duel-boot whenever we want to play this game. But you cannot expect things to work right out of the box. Linux users find it an enjoyable experience to figure out these puzzles on how to get these programs running outside of their native environments. Please show the developers of these softwares some respect and give them patience, for they are not making any money off the work they are doing in all this. Linux is for people who want to rule their computer. Windows is for people who want their computer to rule them. To rule your computer means you must take some time to learn it first.