[MAC] [WINE] "problem launching wow.exe, make sure this launcher is in your wow directory"

[snurfolo]

Hi there, i followed the Wine and Mac instructions but, when it's time launch with the wine command, i get this error:

Quote:

There was a problem launching wow.exe, make sure this launcher is in your wow directory

I tried with both 64 and 32 bit, but it seems that the freakz launcher fails to find wow executables.

Adding realm list and wineing wow.exe directly works, but ofc I get kicked outside after 30 seconds or so from game because I don't use freakz launcher.

Any suggestions?

p.s.: the parallels method works, but my pc is kinda old and wow gets laggy.

[Shocker]

Can you post a screenshot with error + wow folder contents and tell us which .exe you launch?

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[snurfolo]

Here you are.
As you can see I get the same error launching both launchers and I did replace the files in wow folder with files from freakz launcher zip.

http://imgur.com/a/9x9yf

Code:

Last login: Wed Jun 21 12:35:47 on ttys000 MacBook-Pro-di-prova:~ prova$ wine /Users/Shared/WoW_Legion_torrent/launcher_freakz-64.exe Launching WoW Freakz 64bit... There was a problem launching wow-64.exe, make sure this launcher is in your wow directory fixme:ver:GetCurrentPackageId (0x22f6f0 0x0): stub Press any key to continue... MacBook-Pro-di-prova:~ prova$ MacBook-Pro-di-prova:~ prova$ wine /Users/Shared/WoW_Legion_torrent/launcher_freakz.exe Launching WoW Freakz 32bit... There was a problem launching wow.exe, make sure this launcher is in your wow directory fixme:ver:GetCurrentPackageId (0x32fa68 0x0): stub Press any key to continue...

[Shocker]

Can you please try something? Delete wow64.exe and launcher_freakz64.exe, download this https://www.wow-freakz.com/wow/legion/launcher_freakz_test1.zip launcher_freakz.exe, place it in the wow folder, start launcher (it will still give you the error, just click any key to ignore the error) and then start wow.exe (the launcher should get attached to the manually launched wow.exe)

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[snurfolo]

I did
1) remove launcher 64 and wow 64
2) replace launcher with the one from your link
3) wined the new launcher, got usual error
4) wined wow.exe and got kicked as usual

last steps tried twice to be sure

[Shocker]

Sorry, messed up the order: start wow.exe and make sure it's open before you "press any key" to close the launcher

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[snurfolo]

It worked the second time i tried it.
It seems that when I press the infamous any key i have to wait for the system to acknowledge i did it (it takes 15-20 seconds to do it), then i can log in from wow.exe without getting kicked out.

EDIT h19:50m
I keep getting kicked out.
I tried pressing the any key at different phases (before/after logging) but it does not work. :(

EDIT 24th June
FYI I tried the method you posted with the launcher released yesterday. Still getting kicked out.

[MapleDropbear]

I was able to run the launcher through wine launcher_freakz.exe and it gets into game.

But once there it disconnects me saying I didn't launch with launcher_freakz.exe

I am running macOSX 10.15.5

Open to ideas would love to get this running

(i tried deleting the launcher_64 and wow_64 and used the new launcher you had in this this thread to do avail)

open to ideas.


launch text is:

Code:

Launching WoW Freakz 32bit... fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fe58 4 stub Found BuildInfo at 0xEC4A1C Found NetClient::ProcessMessage at 0x6C614A fixme:ver:GetCurrentPackageId (0x57f540 0x0): stub err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not supported in this platform fixme:mpr:WNetGetUniversalNameW (L"Z:\\Applications\\wow\\data\\data", 0x00000001, 0x23c7e0, 0x23c7a0): stub fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported fixme:ver:GetCurrentPackageId (0x32f9c0 0x0): stub fixme:win:EnumDisplayDevicesW ((null),0,0x23ef48,0x00000000), stub! fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x1. fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type. fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend. fixme:win:EnumDisplayDevicesW ((null),0,0x23e908,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23e5d8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23ec18,0x00000000), stub! fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type. fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend. fixme:win:EnumDisplayDevicesW ((null),0,0x23eaf8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23eb78,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23e848,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23efc8,0x00000000), stub! fixme:d3d9:D3DPERF_SetOptions (0x1) : stub fixme:win:EnumDisplayDevicesW ((null),0,0x23e2d8,0x00000000), stub! fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x171df4b8): stub fixme:win:EnumDisplayDevicesW ((null),0,0x23dbc8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23d898,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23dba8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23d878,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23dba8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x23d878,0x00000000), stub! fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not supported in this platform fixme:secur32:schan_get_cipher_algid Don't know CALG for encryption algorithm 4, returning 0 fixme:secur32:schan_imp_get_max_message_size Returning 1 << 14. fixme:secur32:schan_get_cipher_algid Don't know CALG for encryption algorithm 4, returning 0 fixme:secur32:schan_imp_get_max_message_size Returning 1 << 14. fixme:secur32:schan_get_cipher_algid Don't know CALG for encryption algorithm 4, returning 0 fixme:secur32:schan_imp_get_max_message_size Returning 1 << 14. fixme:imm:ImmReleaseContext (0x60066, 0xac9d8b0): stub

[MapleDropbear]

I was able to get it running using the parallels version. It look a little bit but that way works.

[Shocker]

MapleDropbear wrote:

I was able to get it running using the parallels version. It look a little bit but that way works.

More details to help others please?

FREAKZ COMMUNITY @ Facebook
WOW FREAKZ @ Facebook

[MapleDropbear]

Shocker wrote:

MapleDropbear wrote: I was able to get it running using the parallels version. It look a little bit but that way works. More details to help others please?

I got it running as per normal on the mac if I ran windows 10 as a VM using parallels program.

So you go through the numerous steps listed in the how to install parallels which was provided in the install link and then just run as it as I do on the mac. I believe the 32 bit was the one I am using rather than the 64 for mac for whatever reason even though the mac is 64 bit and the windows installed on the VM is also.

The performance is much lower than native but its wow so it doesn't need much to run fairly smoothly.

So yeah, just follow all the steps in the parallels install guide and then just run it locally.

The one thing you will need to do is make sure you install the parallels install tools so you can share the mac folders so you can then copy the mac folders to your PC so you can run it locally. otherwise you'll run into read only issues with folders and ownership which really suck to fix.

[TamerPanda05]

i have the same error with terminal any solutions?
https://imgur.com/a/8b12h

[snurfolo]

@TamerPanda05
It's not a bug, it's a feature. (cit.)
That's how i do.
1) open 2 terminal windows
2) In the first one you write WINE, drag and drop the launcher executable, and press enter once.
3) In the second window you write WINE, drag and drop the wow.exe, and press enter.
4) wait for the game to launch and get to log in screen
5) go back to the first terminal window, the launcher one, and press enter. If everything went smooth you'll see new lines appear in the second window like "fixme:ntdll:EtwRegisterTraceGuidsW register trace class {72b14a7d-704c-423e-92f8-7e6d64bcb92a}"
6) go back to wow, log in and play.

I know it's a bit tedious to do everytime but the game performance is 100x better than the vm one.

p.s.: you need to do this procedure to launch wow. If server crashes and you go back to log in screen you don't need to do it again, just relog.
p.p.s: somehow when i used the launcher it modified itself and cannot be used again. To prevent this i locked it to prevent edits. To do this right click it, select info, in lower part select "prevent edits". You'll see a little lock appear on the launcher icon.

screen

[zaakal]

Hey!

I got this particular problem related to running launcher on Mac with wine. I added the text that the terminals shows me while trying to run the launcher, which should give the overview what's going on. If you need additional information about the ERROR, i happily add more.

Thanks for caring!

The the text that the terminal shows, is following:

Last login: Thu Nov 9 12:38:16 on ttys000
Janars-MacBook-Air:~ janarpilve$ cd desktop
Janars-MacBook-Air:desktop janarpilve$ cd WoW_Legion_torrent
Janars-MacBook-Air:WoW_Legion_torrent janarpilve$ wine /Users/janarpilve/Desktop/WoW_Legion_torrent/Wow.exe
fixme:heap:RtlSetHeapInformation 0x110000 0 0x32fe58 4 stub
Janars-MacBook-Air:WoW_Legion_torrent janarpilve$ fixme:ver:GetCurrentPackageId (0x46f540 0x0): stub
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
Found BuildInfo at 0x141072850
Found NetClient::ProcessMessage at 0x140424AF0
Found ClientServices::Send at 0x140AAA730
Found DataStore::WriteInt8 at 0x140098720
fixme:ver:GetCurrentPackageId (0x8ceed0 0x0): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ntdll:EtwRegisterTraceGuidsW (0x18003cedc, 0x0, {f7b697a3-4db5-4d3b-be71-c4d284e6592f}, 7, 0x18006beb0, (null), (null), 0x18006f840): stub
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {72b14a7d-704c-423e-92f8-7e6d64bcb92a}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {e2091f8a-1e0a-4731-84a2-0dd57c8a5261}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {e8a3bf1f-a86b-4390-9c60-5390b969d22c}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {5727a00f-50be-4519-8256-f7699871fecb}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7e854ec7-cdc4-405a-b5b2-aaf7c9e7d40c}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {79a60dc6-5fc8-4952-a41c-1163aeec5eb8}
fixme:ntdll:EtwRegisterTraceGuidsW register trace class {2718d25b-5bf5-4479-8e88-babc64bdbfca}
fixme:process:GetNumaHighestNodeNumber (0x9cf190): semi-stub
fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not supported in this platform
fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not supported in this platform

Few minutes later i get the following window and the text on it:

The CAS system was unable to initialize: Error downloading versions data from patch service: WOWDOWNLOAD_SERVER_ERROR. URL: http://cdn-wow.freakz.ro/version/EUwow/23420.
Error downloading CDN data from patch service:WOWDOWNLOAD_SERVER_ERROR. URL: http://cdn-wow.freakz.ro/cdnsEUwow/23420.
[/url]

[snurfolo]

zaakal wrote:

...

I'm having the same problem today. I thought it was local so I re-installed wine, but the problem persisted. I came here to check the CAS error but finding your post proved that something is off remotely.

@shocker help us dudebro!

EDIT: all back to normal, it was a CDN problem.
Keep up the good work!