If you’re running HCL Notes/Domino 14.5.1 (marketed as HCL Notes/Domino 2026), a new update just landed. HCL released Fix Pack 1 (FP1) on July 16, 2026. It’s a smaller update than a full version release, but it fixes real problems that admins have been hitting since March.
I wrote about the 12.0.2 Fix Pack 8 upgrade a while back, and that article has been one of our most visited pages since. FP1 for 14.5.1 follows the same pattern: a batch of practical fixes that most shops will want to apply. Let’s walk through what’s actually in it, whether your systems qualify, and how to decide if now is the right time to install it.
Quick Recap: Where 14.5.1 Came From
Before we get into FP1, here’s a fast refresher. HCL Notes/Domino 14.5.1 was released on March 19, 2026. It was a big release. It introduced Domino IQ, HCL’s integrated AI platform/capability, a new Auto-Update feature for pushing out software updates automatically, and support for OIDC (a modern login and security standard). It also brought a cleaner look across Mail, Calendar, and other screens, along with a new default font.
Big releases like this almost always come with a few rough edges. Some features work differently than expected. Some UI elements behave oddly. That’s normal, and that’s exactly what a Fix Pack is meant to clean up.
What’s Actually Inside Fix Pack 1
FP1 is a cumulative update. That means it includes everything that came before it, plus new fixes on top. You don’t need to install anything else first — just make sure you already have 14.5.1 running, and FP1 will layer right on top of it.
Here’s an interesting detail worth knowing. HCL’s official release notice says FP1 fixes about 46 known issues. But if you look at the public Fix List (the detailed technical log HCL keeps), it currently shows 49 entries for this release. That’s not a mistake — the Fix List gets updated on a rolling basis even after the release notice is published, so a few extra entries can show up later. Either way, this is a solid, focused update, not a huge one.
The Fixes You’ll Actually Notice
Most Fix Packs contain dozens of small, technical corrections that only matter to a handful of very specific setups. But a few fixes in FP1 stand out because they touch things regular users and admins run into every day:
- A crash in Preferences. Some users hit a crash simply by clicking More, then Preferences, inside their mail database. This was a regression, meaning it was a bug that got introduced in 14.5.1 itself and is now fixed in FP1.
- A stuck JavaScript editor. Inside Domino Designer, the JavaScript editor sometimes froze for 2 to 4 seconds at a time. Small, but annoying if you’re doing a lot of scripting work.
- Search Center text disappearing. After using “Search This View,” the text you typed into Search Center would stop showing up in the search bar. Fixed in FP1.
- Broken S/MIME attachments. If a recipient’s mailbox was over its storage quota, an encrypted S/MIME email could arrive unreadable, and its attachment would be lost entirely. That’s now fixed.
- Delivery notifications not following the rules. Domino’s automatic “your message couldn’t be delivered” notifications weren’t formatted the way the email standard (RFC 3464) requires. Now they are.
- A security issue with OIDC. Certain server commands were breaking chained OIDC login setups, which in turn broke Domino’s own OIDC provider function. This is now resolved.
A Fix That Matters If You’re Using Domino IQ
Since Domino IQ is still new, it’s worth calling out separately. FP1 fixes a bug where, if Domino IQ was running in Remote mode, a setting called DominoIQ.Config.ModelFileName wasn’t being recorded correctly. If you’ve already started experimenting with Domino IQ on your server, this is a fix worth having.
Sametime Chat Fixes
If your organization uses the embedded Sametime chat inside Notes, FP1 includes several small but welcome fixes:
- The chat window no longer steals your cursor’s focus when a new message comes in.
- The web-based chat window no longer refreshes itself unexpectedly.
- A bug that sometimes created a random group chat with only one participant is fixed.
- Your presence status (Available, Away, etc.) now updates properly based on actual keyboard and mouse activity.
- Auto-login now works correctly when clicking a chat link in supported languages.
None of these are dramatic, but if your team relies on Sametime daily, they’ll notice.
Updated Java runtime
FP1 also upgrades the bundled JVM to Semeru JDK 21.0.11+10 and updates timezone data to 2026b. This is easy to overlook, but it’s one of the more significant platform-level changes in the Fix Pack.
Is Your System Even Eligible?
Before you plan the upgrade, double-check that your platform is supported. HCL confirmed the following for FP1:
Windows: Windows 10, Windows 11, Windows Server 2019, 2022, and 2025. All 64-bit only — there’s no 32-bit support here.
Although Windows 10 remains listed in HCL’s system requirements, organizations should also consider Microsoft’s lifecycle status when planning new deployments. Windows 10 being listed as supported does not mean Windows 10 itself is a good strategic platform choice because Microsoft ended normal Windows 10 support in October 2025.
macOS: Sonoma (14.x), Sequoia (15.x), and the newer Tahoe (26.x). macOS Tahoe 26.x is supported, including systems using Apple’s newer M4 and M5 silicon.
Virtual environments: Citrix Virtual Apps & Desktops 7.1912 and later, Citrix XenApp 7.15, VMware VDI 7, VMware Horizon 7.13 and 8, and Microsoft RDS 2019/2022 are supported configurations. However, these platforms have restrictions—for example, Domino Designer and Domino Administrator clients aren’t supported in these virtualized configurations.
Linux: SUSE Linux Enterprise 15 SP6 is supported, but here’s a heads-up — you’ll likely see a warning message during installation. Don’t panic. The configuration is officially supported, the installer just flags it as a caution.
If your team is still running Notes 14.0 FP4 or 12.0.2 FP6, note that FP1 for 14.5.1 doesn’t apply directly to you — you’d need to move to 14.5.1 first before this Fix Pack becomes relevant.
How to Install It
The process itself is simple:
- Confirm you already have HCL Notes/Domino 14.5.1 installed. FP1 installs on top of it — it is not a standalone installer.
- Download FP1 from the HCL Software Downloads portal.
- FP1 is cumulative and language-independent; however, Fix Packs do not contain translation fixes.
- Apply it the same way you’d apply any Fix Pack — test it on a non-production server first if you can.
A Quick Word on Testing Before You Roll This Out
It’s tempting to push a Fix Pack out to everyone the same day it’s released, especially when it fixes crashes and annoying bugs. But a little patience goes a long way here. A few simple steps can save you a headache later:
- Apply it to a test or staging server first, if you have one. Even a spare VM works fine for this.
- Open your most-used custom applications after the update and click through the basics — views, forms, any custom action buttons. This is exactly the kind of thing that can quietly break after an upgrade, as we’ll cover in the callout box below.
- Check your Sametime setup if your team relies on chat. The Sametime fixes in this release touch things like auto-login and presence status, so it’s worth confirming those still behave the way your users expect.
- Give it a few days on staging before pushing to production, especially if you manage a large or complex Domino environment with lots of custom development.
None of this needs to be a big formal process. For most small and mid-sized shops, two or three days casual testing might be enough to catch anything unusual before it reaches your whole user base.
Should You Upgrade Right Now?
Here’s the honest, practical answer, broken down by where you’re starting from.
If you’re already on 14.5.1: Yes, go ahead and apply FP1. HCL itself recommends it for all customers. Most of what’s inside are small quality-of-life and stability fixes, and there’s nothing in the fix list suggesting FP1 introduces new problems. Schedule it in during your next normal maintenance window, test it against your own applications first, and roll it out.
If you’re still on an older version, like 12.0.2 or 14.0: You have a decision to make. You could jump straight to 14.5.1 and then immediately apply FP1, giving you the most current, most stable version in one move. Or, if your environment is complex, you might want to stage the upgrade — get comfortable on 14.5.1 first, confirm your custom applications behave correctly, and then apply FP1 once things are settled. If you followed our earlier guide on upgrading through 12.0.2 Fix Pack 8, this is the logical next stop on that same path.
If you’re evaluating whether to upgrade to 2026 at all: FP1 is actually a good argument in favor. A number of the rough edges that came with the big March release — the kind of thing that makes IT teams nervous about early adoption — are already smoothed out here. Four months after release, with a solid Fix Pack behind it, 14.5.1 is a safer bet today than it was at launch.
My honest recommendation: schedule it, don’t rush it. Test it against your own custom applications and templates first, especially anything with heavy XPages or LotusScript customization, before pushing it out to your whole organization.
A related fix worth knowing about: the disappearing ($Inbox) action button
While we’re talking about Domino upgrades, here’s a real issue we ran into and fixed. If a custom action button on your
($Inbox)view keeps disappearing after a while, it’s likely not a bug — it’s Domino’s nightly Design task quietly overwriting your view with the stock template. The fix: open the view in Domino Designer and enable “Prohibit design refresh or replace to modify” on that specific view. This stops the nightly task from wiping out your customization. It’s a good habit to check for this on any custom views right after an upgrade, since design refresh behavior can sometimes reset things you don’t expect.
What About the Next Fix Pack?
If history is any guide, HCL will keep releasing Fix Packs for 14.5.1 every few months, the same way it did for 12.0.2. Each one will likely fix a fresh batch of small issues that only show up once thousands of real users are clicking around in real environments. That’s normal, and it’s actually a good sign — it means the platform is still being actively maintained and improved, not left to sit. We’ll keep this article updated, and we’ll cover the next Fix Pack here too when it lands.
Frequently Asked Questions
Is HCL Notes/Domino 14.5.1 Fix Pack 1 mandatory?
It’s not mandatory in a technical sense — your server will keep running without it. But HCL recommends it for all customers, and most of the fixes address real, everyday problems, so there’s little reason to skip it.
Do I need to enroll in the Early Access or Beta program to get FP1?
No. FP1 is a standard release available to all licensed customers through the HCL Software Downloads portal. The Early Access program was only needed for testing 14.5.1 before its official March 2026 launch.
What if I’m still running Notes 14.0 FP4?
FP1 for 14.5.1 only applies once you’re on 14.5.1. You’ll need to upgrade to 14.5.1 first before this specific Fix Pack becomes relevant to you.
Does Fix Pack 1 change anything about Domino IQ?
Yes, slightly. It fixes a bug affecting a configuration setting when Domino IQ runs in Remote mode. It does not introduce a major new Domino IQ capability; the relevant Domino IQ change in FP1 is a fix to the DominoIQ.Config.ModelFileName statistic when running in Remote mode.
Will installing FP1 disrupt my custom applications?
It shouldn’t, since Fix Packs are built to be low-risk. Still, it’s good practice to test on a non-production server first, especially if you have heavily customized views, XPages applications, or LotusScript agents.
