PowerBuilder 2025 R2: What's New, and Should You Upgrade?

Appeon shipped PowerBuilder 2025 R2 on 3 June 2026, and for existing customers it is a free upgrade. It is a revision release — it builds on the 2025 line rather than replacing it — but the substance is real: a modernized IDE, genuine security hardening, and forward database compatibility that quietly removes a few upgrade blockers. Here is what actually changed, why it matters for a production system, and whether it is worth scheduling.

What actually changed

R2 lands in three buckets. None of them is a headline-grabbing new paradigm; together they are a solid, defensive release aimed at the people who maintain PowerBuilder applications every day.

1. A modernized IDE

This is the part working developers will feel first:

• Dark mode and IDE themes, with customizable syntax colouring — the single most-requested quality-of-life change in years.
• Up to 50% lower memory usage in Solution mode, plus faster application loading and more flexible incremental builds.
• Better source control: Git Fetch and Rebase directly in the IDE, the current branch name shown in the status bar, and source-control history preserved when converting a Workspace to a Solution.
• Code-editor improvements — stronger code intelligence, formatting and navigation.

2. Security hardening

The security work is the most enterprise-relevant part of the release, because it produces answers you can hand to an auditor:

• Modern executable mitigations — SafeSEH, DEP, ASLR and CFG can be enabled in Appeon-compiled executables to defend against memory-based attacks (currently flagged beta).
• Modern cryptography — the CrypterObject gains AES-GCM (with AAD) and RSA-PSS signatures, plus expanded SHA2/SHA3 hashing.
• Enhanced DLL-loading security and the ability to sign native client/server applications from the project painter.

3. Forward platform and database compatibility

This bucket is quiet but strategically important — it removes reasons the application can block a platform upgrade:

There is also an emerging-tech nod: a beta PyPb capability for calling Python from PowerBuilder through a .NET assembly — early, but a signal of where Appeon is pointing.

Why this release matters for a production system

Read past the feature list and R2 speaks to three things that actually keep enterprise PowerBuilder owners up at night:

1. Developer experience is a retention tool. The pool of PowerBuilder developers is shrinking, so anything that makes the IDE pleasant to work in — dark mode, lower memory, smoother Git — quietly helps you keep and attract the people who maintain the system. (More on that in is PowerBuilder dead in 2026?)
2. Security mitigations are audit ammunition. For internet-facing or regulated systems, “we run modern EXE hardening and current cryptography” is a far better answer in a security review than silence. R2 gives you that answer.
3. Database compatibility unblocks the DBA team. When the application can follow Oracle to 26ai or SQL Server to 2025, the PowerBuilder app stops being the reason a platform upgrade is stuck — the exact bottleneck we describe in PowerBuilder + Oracle compatibility.

Should you upgrade?

Line your situation up against three cases.

1. Already on PowerBuilder 2025. Yes — take it. It is a free, in-place revision with real security and IDE gains and low migration risk. The prudent test list before rollout: third-party controls and OCX components, printed and PDF DataWindow output, and high-DPI rendering on your users' actual monitors.
2. On an older Appeon line (2019–2022). R2 does not change the upgrade decision, but it makes 2025 a more attractive landing target — you gain the hardening and compatibility in one hop. See the version and support-lifecycle reference for where your version sits.
3. On Sybase-era PowerBuilder (9–12.6). The calculus is unchanged, but the destination just got better. Plan the leapfrog to current PowerBuilder using our 9 → 2025 upgrade guide and land on 2025 R2.