You may encounter the following known issues in this release. We are working diligently to resolve them in the coming releases.
PowerBuilder
PowerBuilder 2025 R2 Build 6430 has the following known issues.
-
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 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.6430 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 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.
-
When Virtual Space is enabled in Code Editor, Word Wrap does not take effect.
-
In PowerBuilder IDE, when objects or the library list of the application change (for example, objects/libraries are added or removed), the auto-completion list of the AutoScript feature does not reflect those changes until PowerBuilder IDE is restarted or the target is reloaded.
-
When System Tree is configured not to open by default when PowerBuilder IDE starts, the Navigate Backward/Forward feature remains disabled until System Tree is opened.
-
In PowerBuilder IDE, after a project is created by using the wizard, it crashes when executing Deploy from the System Tree.
Workaround: The issue can be avoided by making any changes in the project and then save it.
-
After setting the window's Icon property to an SVG file, the Icon property value may be lost when reopening the window in some cases while running the application in the PowerBuilder IDE. This issue does not occur when running the application in runtime.
-
When multiple variables of the same type are declared in a single statement and one variable is initialized using a function call, the variables declared after that initialized variable do not appear in the AutoScript auto-completion list.
PowerServer
PowerServer 2025 R2 Build 6430 has the following known issues.
-
The following warning may occur in PowerServer Web API compilation if "Use external Microsoft Entra ID Service" is used for Web API authentication.
Warning message: warning NU1903: Package 'Microsoft.AspNetCore.DataProtection' 10.0.0 has a known high severity vulnerability, https://github.com/advisories/GHSA-9mv3-2cwr-p262
To solve this issue, please modify the <PowerServer_WebAPI_Solution_location>\salesdemo_cloud\UserExtensions\Authentication\Authentication.xml file as follows:
<PackageReference Include="Microsoft.AspNetCore.DataProtection" Version="10.0.7" />
<PackageReference Include="System.Security.Cryptography.Xml" Version="10.0.7" />
