I think that I see your image display problem. I would recommend getting rid of all the "Path" references to any image. Either use relative path'ing or my favourite ... nopath with the images all loaded into a PBD/DLL via a PBR file. I'm using both techniques I described above now in my PowerClient and PowerServer 2021 testing and have no DWO image display issues. Food for thought.
"Another option would be to have the images in the same folder as the PBL where your application is in and then not specify any path in the datawindow:
Instead of: "L:\EXE\BMP\pb_icon_edit.png"
You could also use a PBR file, but I understand that you want the images to be 'dynamic' so you can change the image without having to build a new executable. (since you specified them as dynamically loaded images in the ps project).
Glad you solved your problem though, please mark as "answered / resolved".
Also, if L: drive is a network drive, maybe you'd have to set some registry values to enable UNC paths. Save this following text as a .REG file and double click on it on the user's computer to enter the value into the windows registry:
Windows Registry Editor Version 5.00
If the images do NOT have to be 'dynamic', you can use a PBR file and then the images won't have to be anywhere when you distribute the EXE, they'll be present within the EXE (or any PBD to which you could assign the pbr when building the executable).