You may encounter the following known issues in this release. We are working diligently to resolve them in the coming releases.
-
Using .NET related features, such as ADO.NET Database Interfaces or Call .NET Assembly, after switching to earlier runtime versions of 2025/2025 R2 in PowerBuilder 2025 R2 Beta3 causes the IDE to crash due to part of the environment has been loaded with .NET 10.0 by the new PB250.exe. To resolve this issue, you may copy the following 4 JSON files from the Runtime 25.1.0.6373 folder to the folder of the runtime version you switch to so that the environment required by the .NET features is loaded by .NET 10.0 as well.
-
Appeon.DB.Proxy.runtimeconfig.json (both 32-bit and 64-bit)
-
pbdotnetinvoker.runtimeconfig.json (both 32-bit and 64-bit)
-
-
The following core files in PowerBuilder 2025 R2 Beta3 has been updated from 14.38.33135.0 (VC++ 2022) to 14.50.35719.0 (VC++ 2026). If there are files of lower versions with identical names in the operating system, they will be loaded at higher priority and thus causes the PowerBuilder deployed application to throw errors at runtime.
-
For 32-bit: vcruntime140.dll, concrt140.dll, msvcp140.dll
-
For 64-bit: vcruntime140.dll, vcruntime140_1.dll,concrt140.dll, and msvcp140.dll
You may adopt either of the workarounds below to resolve this issue:
-
Install Microsoft Visual C++ Redistributable 2026.
-
Copy the core files mentioned above to the same directory as the EXE file of the PowerBuilder deployed application.
-
-
After using GIT source control, it takes about 8 seconds to expand a PBL containing more than 500 objects for the first time in the system tree. This issue is due to the time required for the underlying library to refresh the status of all object.
-
The PrintBitmap method currently does not support SVG rendering.
