Recently on my Windows PC (Windows 11 for arm 64), old version 8.D.2.6 of AWE Designer (which I used for some years) fails to launch.
Right after AWE Server boots, it disappears and AWE Designer emits following error:

So I updated to the latest one, 8.2025.3, and am facing awb file compatibility issue.
With my AWECoreOS library implementation,
attached 2MicTalkTo_0_0_4.0 loads successfully (which was built with the old AWE designer),
but attached 2MicTalkTo_0_0_4.1 cannot be loaded (which was built using the latest AWE designer).
The error message is as follows:
The layout .../AWECoreOS/Designs/2MicTalkTo_0_0_4.1.awb downloaded unsuccessfully at position 1 with error = Unknown error -39
AWECoreOS version info is as follows:
```
AWECore cortexa Build
Built on: Thu Nov 07 15:41:03 EST 2024
Build name: release.awe.cortexa-2181
Built from: awecore-common
Version: AC-8.D.8_ACOS-8.B.18
SHA: ed4bad1
AWECore CortexA cortexa Build
Built on: Thu Nov 07 15:41:07 EST 2024
Build name: release.awe.cortexa-2181
Built from: awecore-cortexa
Version: v15
SHA: db3c4f7
cortexa Build -- Toolchain Info: [aarch64-gcc-arm-10.2]
Built on: Thu Nov 07 15:41:10 EST 2024
Build name: release.awe.cortexa-2181
Built from: dspc-cmake-toolchains
Version: master
SHA: 56770da
Recipe File Used: AC-8.D.8_ACOS-8.B.18_VUI_Prod.recipe
Built on: Thu Nov 07 15:41:13 EST 2024
Build name: release.awe.cortexa-2181
Built from: awecore-recipes
Version: master
SHA: fdac07f
AWECore Build -- Module Set: awe-mod-dspc-vui
Built on: Thu Nov 07 15:41:16 EST 2024
Build name: release.awe.cortexa-2181
Built from: awe-mod-dspc-vui
Version: VUI-1.2.13
SHA: 8c7959e
```
Could anyone help resolving my issue?
Best regards,
Takashi
5:29pm
Hi,
When you say it stopped working, do you mean that it used to work on your ARM Windows laptop, and it stopped one day, or did it stop when you started using the ARM Windows machine?
We have seen the "line 129" issue when using Remote Desktop. Are you using Remote Desktop?
Does the older AWB load OK using the new AWE Server? I presume the error message you showed was from AWE Server.
Thanks,
Gary W.