WowClassic-ARM64.exe is gone, WoTLK Classic can no longer be launched from Windows on ARM devices

Support Technical Support
1

Until yesterday, I was still playing with WoTLK Classic on my Windows on ARM device. There is a WowClassic-ARM64.exe in the World of Warcraft/classic Folder to make everything run well.

But today’s update completely deletes the WowClassic-ARM64.exe, making the game cannot be launched again. I tried to reinstall the game completely, but WowClassic-ARM64.exe or its x64 version Wowclassic.exe still did not appear. This completely prevented WoTLK Classic running on Windows on ARM devices.

I checked the online storage with CASCExplorer and found that Wowclassic-ARM64.EXE has disappeared from Blizzard CDN. Is this a technical error? Will WoTLK Classic continue to support Windows on ARM device?

The retail realm is still available at Windows on ARM devices at current. I have Wow-ARM64.exe in the retail folder and it works well.

Wow*-ARM64.exe’s existence in each services:

  • retail: Wow-ARM64.exe
  • retail_ptr: WowT-ARM64.exe
  • retail_beta: WowB-ARM64.exe
  • classic: missing
  • classic_ptr: missing
  • classic_beta: WowClassicB-ARM64.exe
  • classic_era: WowClassic-ARM64.exe
  • classic_era_ptr: WowClassicT-ARM64.exe

From CASCExplorer (Online Storage) at EST 08:00.

3 Likes
2

so thats what happened… there goes my day…

3

Do you run Win 11? AFAIK with Win 11, you should be able to launch x86 64-bit apps on WoA (although with some performance penalty).

With luck, it’s just a build / packaging error.

4

I tried the x64 version of WowClassic.exe, but the game window did not appear and only this:

Your 3D accelerator card is not supported by World of Warcraft. Please install a 3D accelerator card with dual TMU support.

As far as I know, the GPU acceleration has not been supported by the x64 emulation of Win11 on ARM, so WoA devices have no chance to run x64 3D games.

The GPU acceleration is supported in x86 emulation, but World of Warcraft no longer provides the x86 executable.

So WowClassic-ARM64.exe is currently the only way to launch WotLK Classic in WoA devices. I need it to come back.

5

any update please lol

6

We’re looking into this now. Wrath arm64 windows client is supposed to be there

1 Like
7

Thank you guys so much!! If you are able to give us a batch of files for us to download and manually install that would be amazing! If not then hopefully ital be fixed soon.

8

More likely, they will push out the correction in a client update, I suspect.

9

I am having the same prob. Hopfully you fix this soon. I am missing out on hallows end. Please update us as soon as this is fixed

10

Could you retry the build we just pushed? I believe this build has the correct executable.

11

I did the update. Still isnt working. Do i need to uninstall and reinstall it. Again…

12

The latest build is still not fixed. I did a reinstall and still no executable.

13

I haven’t tried it myself, but my friend gave me some feedback.

  • 10 hours ago, he got WowClassic-ARM64.exe through Battle.net update and can launch the game.
  • 7 hours ago, the file was deleted again by the Battle.net update and cannot launch the game.

He didn’t backup his WowClassic-ARM64.exe and he didn’t think he would lose it again.
I would appreciate if someone could share this WowClassic-ARM64.exe.

By looking at CASCExplorer online storage wow_classic, there is no WowClassic-ARM64.exe on the Blizzard CDN.

14

I’m also having this problem. Wotlk classic wont launch, but retail will. I’ve uninstalled & reinstalled the game but that didn’t fix the problem.
In the classic folder there is an application named “Blizzarderror”

15

Eventually I found a working exe and I extracted it from the Wow Classic Beta online storage with CASCExplorer-v1.0.176 (newer versions don’t work).

It’s WowClassicB-arm64.exe and has a green icon, but it has the same version 3.4.0.46158 as the WotLK production server. So as long as we rename it to WowClassic-arm64.exe, we can use it on the production server.

You can download it here:

https://drive.google.com/drive/folders/1HDIEIGWpDj1gqZtMqN9igwAxa3CvaIeY

Or extract it yourself. After clicking the exe in CASCExplorer, the interface may become unresponsive. Disabling “View > Show preview” can solve the problem. Once the exe is selected, right-click and select Extract.

16

There was another unrelated issue that made us have to roll back the build to the build without the arm64 executable. We’re still working on a proper fix

17

Maybe some WoA users will come to this thread, and I take the opportunity to ask if anyone is using a device with a Qualcomm Adreno 630 GPU and is experiencing the same DX12 graphics issues as I am.

I have an “unofficial” WoA device which is a Xiaomi Mi Mix 2S phone which flashed with a special firmware. lol. (thanks Renegade Project.)

I know it’s not supported by Microsoft, and most likely not by Blizzard. So I just wanted to ask if anyone with an “official” WoA device had a similar problem as me. Especially devices with Qualcomm Snapdragon 850 SoC like Lenovo Yoga C630.

The Mi Mix 2S has a Snapdragon 845 SoC, and the Snapdragon 850 is an overclocked version of it. But the Snapdragon 850 has official Windows 11 support. So as you can imagine, the Windows driver used by my Mi Mix 2S is modified from the version prepared for Snapdragon 850 devices. Both also have nearly identical Adreno 630 GPUs.

So if someone’s having the same problem as me with a Snapdragon 850 device, it’s a proof that the problem is with the Qualcomm driver or Wow, not my “unofficial” device.

What’s wrong with my game?

In the first few minutes of launch, WotLK was running fine with DX12. FPS can be stabilized at 60 with 50% rendering resolution (1080x540, it’s clear enough for phones) and graphics quality level 2.

But after a few minutes, the game window suddenly disappears. When the window reappears, the FPS is less than 30, and even less than 10 in a crowded place!

The gx.log shows nicely what happened: the game was running on DX12 at first. But the DX12 command queue suddenly became unresponsive, so the game switched to DX11 and the framerate plummeted.

Note: It’s not a beta client specific issue, I’ve had this problem for a long time. The Retail client has the same problem.

I can’t say whose fault this is, after all my game runs on a unverified driver and a unverified device. But it works, so that’s cool - not always smooth though.

So I’m looking forward to getting your feedback from others running on verified drivers and devices. Thanks for anyone’s feedback.

gx.log from WotLK client:

10/21 00:13:43.669  LogOpen
10/21 00:13:43.669  World of Warcraft BetaRetail ARM64 3.4.0.46158
10/21 00:13:43.669  Windows 11 (10.0.22623) arm64
10/21 00:13:43.669  Snapdragon 845 | Sockets:1 Cores:8 Threads:8
10/21 00:13:43.669  5.6 GB System Memory
10/21 00:13:43.669  On Battery - Battery Present (80%)
10/21 00:13:43.754  Adapter 0: "Qualcomm(R) Adreno(TM) 630 GPU" family:Unknown type:Integrated vendor:0x4351 device:0x3230 driver(0x1a001229ea0000) location:0 dx11:true dx12:true
10/21 00:13:43.754      Monitor 0 "Generic PnP Monitor" Size(2160x1080) Pos(0, 0)
10/21 00:13:43.803  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 00:13:43.803  D3d12 Device Create
10/21 00:13:43.803  DXGI_FEATURE_PRESENT_ALLOW_TEARING:true
10/21 00:13:43.912  DXGI_FORMAT_B8G8R8A8_UNORM UAV support: true
10/21 00:13:43.914  Ray Tracing Support: None
10/21 00:13:43.914  Variable Rate Shading Supported: false
10/21 00:13:45.585  NotifyOnDeviceCreate
10/21 00:13:45.626  D3d12 Device Create Successful
10/21 00:13:45.626  Using shader family dx_5_0
10/21 00:13:45.626  <IsGPUDriverOutOfDate> No
10/21 00:13:45.626  Detected Graphics Defaults: 2 (CPU = 7, GPU = 2, MEM = 5) WindowSize: 1080x540
10/21 00:13:45.968  Render Settings Changed. New Render Size: 1080x540 (2160x1080 @ 50.0%)
10/21 00:13:47.987  Render Settings Changed
10/21 00:21:11.328  Error WaitForSingleObjectEx Timeout: The wait operation timed out. (0x80070102).
10/21 00:21:11.359  Device context was lost. Attempting recovery. Occurrence: 1
10/21 00:21:11.359  GxRestart
10/21 00:21:11.359  D3d12 Device Destroy
10/21 00:21:11.547  NotifyOnDeviceDestroy
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:11.609  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 00:21:12.203  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 00:21:12.203  D3d12 Device Create
10/21 00:21:12.203  DXGI_FEATURE_PRESENT_ALLOW_TEARING:true
10/21 00:21:12.203  Error D3D12 Create Device failed: The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. (0x887A0006).
10/21 00:21:12.203  D3d12 Device Create Failed
10/21 00:21:12.203  D3d12 Device Destroy
10/21 00:21:12.203  NotifyOnDeviceDestroy
10/21 00:21:12.235  Trying DX11
10/21 00:21:12.297  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 00:21:13.176  NotifyOnDeviceCreate
10/21 00:21:22.931  Dx11 Device Create Successful
10/21 00:21:22.931  Using shader family dx_5_0
10/21 00:21:22.931  <IsGPUDriverOutOfDate> No
10/21 00:21:22.931  Render Settings Changed
10/21 00:23:59.434  Dx11 Device Destroy
10/21 00:23:59.434  NotifyOnDeviceDestroy
10/21 00:24:01.248  GxShutdown

gx.log from Shadowlands client:

10/21 01:22:46.890  LogOpen
10/21 01:22:46.890  World of Warcraft Retail ARM64 9.2.7.45745
10/21 01:22:46.890  Windows 11 (10.0.22623) arm64
10/21 01:22:46.890  Snapdragon 845 | Sockets:1 Cores:8 Threads:8
10/21 01:22:46.890  5.6 GB System Memory
10/21 01:22:46.890  On Battery - Battery Present (50%)
10/21 01:22:47.027  Adapter 0: "Qualcomm(R) Adreno(TM) 630 GPU" family:Unknown type:Integrated vendor:0x4351 device:0x3230 driver(0x1a001229ea0000) location:0 dx11:true dx12:true
10/21 01:22:47.027  	Monitor 0 "Generic PnP Monitor" Size(2160x1080) Pos(0, 0)
10/21 01:22:47.067  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 01:22:47.067  D3d12 Device Create
10/21 01:22:47.067  DXGI_FEATURE_PRESENT_ALLOW_TEARING:true
10/21 01:22:47.203  DXGI_FORMAT_B8G8R8A8_UNORM UAV support: true
10/21 01:22:47.203  Ray Tracing Support: None
10/21 01:22:47.203  Variable Rate Shading Supported: false
10/21 01:22:48.755  NotifyOnDeviceCreate
10/21 01:22:48.848  D3d12 Device Create Successful
10/21 01:22:48.848  Using shader family dx_5_0
10/21 01:22:48.848  <IsGPUDriverOutOfDate> No
10/21 01:22:48.852  Detected Graphics Defaults: 2 (CPU = 7, GPU = 2, MEM = 5) WindowSize: 1080x540
10/21 01:22:49.502  Render Settings Changed. New Render Size: 1171x528 (2109x951 @ 55.6%)
10/21 01:22:58.869  Render Settings Changed
10/21 01:23:19.297  Render Settings Changed. New Render Size: 600x300 (1080x540 @ 55.6%)
10/21 01:23:26.166  Render Settings Changed. New Render Size: 1200x600 (2160x1080 @ 55.6%)
10/21 01:25:19.508  Error DeviceRemoved: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
10/21 01:25:19.508  Device Removed Reason: The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. (0x887A0006).
10/21 01:25:19.508  Error CpuResolveOcclusionQueries Map Failure: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005).
10/21 01:25:19.508  Device Removed Reason: The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. (0x887A0006).
10/21 01:25:19.536  Device context was lost. Attempting recovery. Occurrence: 1
10/21 01:25:19.536  GxRestart
10/21 01:25:19.536  D3d12 Device Destroy
10/21 01:25:19.536  NotifyOnDeviceDestroy
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:19.554  Error RealCloseSingle failed: Unspecified error (0x80004005).
10/21 01:25:20.061  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 01:25:20.061  D3d12 Device Create
10/21 01:25:20.061  DXGI_FEATURE_PRESENT_ALLOW_TEARING:true
10/21 01:25:20.061  Error D3D12 Create Device failed: The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. (0x887A0006).
10/21 01:25:20.061  D3d12 Device Create Failed
10/21 01:25:20.061  D3d12 Device Destroy
10/21 01:25:20.061  NotifyOnDeviceDestroy
10/21 01:25:20.074  Trying DX11
10/21 01:25:20.134  Choosing low power gpu: "Qualcomm(R) Adreno(TM) 630 GPU"
10/21 01:25:20.173  NotifyOnDeviceCreate
10/21 01:25:25.051  Dx11 Device Create Successful
10/21 01:25:25.051  Using shader family dx_5_0
10/21 01:25:25.051  <IsGPUDriverOutOfDate> No
18

I’m on an Ayn Odin running W11 Arm and my wow will crash DX12, like bluescreen to bootloader crash. The only semi stable has been dx11, not dx11 legacy either, and at 2 preset, I get 25fps tops.

DX12 gets closer to 50fps, while at native res, but lasts a whopping 30 seconds before bluescreening, hard.

1 Like
19

This is really trying my patience. For a game I pay money to play monthly, I expect to be able to play it whenever I want during any point of that month. Especially when there is a once a year event going on and certain achievements need to be met to acquire special/ rare mounts. I am becoming overwhelmed with this and feeling like blizzard doesn’t actually care about individual customers. Once again this is a time is against me meeting certain goals. This needs to be addressed. Immediately.

1 Like
20

I have Snapdragon 850 device so I can check it out. Planning to test also Snapdragon 8c. Previously the performance was really poor.

1 Like