Starting from hwc 3.1.40 executables are swapped

[loafoe]

We are debugging an issue for a customer who is using hwc-buildpack. Their app works fine with Buildpacks 3.1.39 and below. Things start failing with 3.1.40 and beyond. One observation we made is that the bundled hwc is upgraded from 27.0.0 to 40.0.0 in the 3.1.40 buildpack. The hwc package contains 2 executables for different architecture (x86 and amd64). However, the newer hwc package have swapped the binary types names:

hwc_27.0.0_windows_x86-64_any-stack_4c27dcc4.zip

$ file hwc.exe
hwc.exe: PE32+ executable (console) x86-64, for MS Windows

$ file hwc_x86.exe
hwc_x86.exe: PE32 executable (console) Intel 80386, for MS Windows

For the newer hwc zip files this is now reversed:

hwc_40.0.0_windows_x86-64_any-stack_50a230d2.zip

$ file hwc.exe
hwc.exe: PE32 executable (console) Intel 80386, for MS Windows

$ file hwc_x86.exe
hwc_x86.exe: PE32+ executable (console) x86-64, for MS Windows

Could this be impacting the compatbility of deployed apps?

[loafoe]

@arjun024 any ideas on above?

[gsidhwani-nr]

I have also detected the same problem . Is latest release also available in Tanzu Cloud Foundry for windows ?

[ragnaray]

Request cloudfoundry to kindly release the hwc buildpack release 3.1.46 as soon as possible. Our teams are blocked on the executable issue raised by @loafoe above since July 2 2025.

[loafoe]

@arjun024 any idea when a new buildpack will be released? The last working version is from Sep 23, 2024 (3.1.39)

[loafoe]

@arjun024 it looks like 3.1.47 is still broken in the same way as described above, can you please confirm?