FlexiCapture 12 Release 4 Update 9 (Build #12.0.4.1209)

⚠️ Customers must update local FlexiCapture components after this release

  • Following deployment of this release to FlexiCapture Cloud, customers must update their locally installed FlexiCapture client components to Release 4 Update 9. 
  • Customers using existing IMAP or GraphMail Image Import Profiles must also sign in to each affected profile again after completing the update.

Release Date: September 2026

The following improvements have been made for this release:

🛠️ Updating Code signing certificate for Windows binaries in FlexiCapture


🛠️ Client secret dependency removal in FlexiCapture for Microsoft OAuth2 processing


🛠️ Upgraded ICAAS Function Apps Runtime environment to .NET 10 Isolated


🛠️ FlexiCapture documentation migrated to docs.abbyy.com site from help.abbyy.com


🛠️ The Bug Fixes section lists the issues that have been fixed in FlexiCapture in this release
 

💡Updating Code signing certificate for Windows binaries in FlexiCapture (664295, 664297)
 

💡FlexiCapture ICAAS cannot assemble documents that have more than 30 pages. This is now increased to support upto 100 pages (666848, 667822)
 

💡Client secret dependency removal in FlexiCapture for Microsoft OAuth2 processing (n/a) 
 

💡Updating Web help links from help.abbyy.com to docs.abbyy.com pages in all FlexiCapture components (n/a)

🪲 Resolved collation conflict in dbo.User_GetAvailable after DB upgrade (667101, 668220)
 

🪲 Exception Queue Tasks Inaccessible in Web Verification Station After Send to Stage (672932)
 

🪲 Prefer PDF text layer if available is not used during recognition (574484, 656210)
 

🪲 Access denied error when filtering batches as a Senior Verification Operato (656997, 657148, 679273)
 

🪲 500 Sharing Violation error when exporting (627018, 655856, 667234, 676906, 630499)
 

🪲 Some old full-width numbers appear unexpectedly during editing at Web verification station with CJK IME editor (677555)

❗Windows may display a Microsoft Defender SmartScreen warning during installation

  • When you run the FlexiCapture installer, Windows may display the message "Windows protected your PC — Microsoft Defender SmartScreen prevented an unrecognized app from starting." The installer in this release is signed with a refreshed ABBYY code-signing certificate. 
  • Microsoft Defender SmartScreen builds trust for a newly signed file based on how widely it has been downloaded, so a recently issued signature is flagged as unrecognized until that reputation accumulates. 
  • To verify the file is genuine, right-click the installer, select Properties → Digital Signatures, and confirm ABBYY is listed as the signer. Then select More info → Run anyway to continue. The warning stops appearing as reputation builds.

If antivirus software actively blocks or quarantines the installer, that is a different problem. Send that one to ABBYY support.

❗Unblock the installer before running it on Windows Server

  • Windows marks files downloaded from the internet as untrusted. 
  • On Windows Server 2025, this can stop the installer when it deploys distributed components, and the installation wizard will not continue. 
  • Before you run the installer, right-click the downloaded file, select Properties, select the Unblock checkbox on the General tab, and click Apply. 
  • If you downloaded an archive, unblock the archive before extracting it so that every extracted file is cleared. The installation then completes normally. 
Unblock the archive

‼️ REQUIRED: Update local FlexiCapture components after this release

  • Following deployment of this release to FlexiCapture Cloud, customers must update their locally installed FlexiCapture client components to Release 4 Update 9. 
  • Customers using existing IMAP or GraphMail Image Import Profiles must also sign in to each affected profile again after completing the update.

❗ With this release, the client secret dependency has been removed from FlexiCapture’s Microsoft OAuth2 processing 

  • For existing Image Import Profiles (IMAP, GraphMail) users must re-login once after the release.
  • This one-time login ensures that the token refresh mechanism functions seamlessly going forward.
  • After re-authentication, the fix will apply correctly, and imports will continue without repeated login prompts
  • Following deployment of this release to FlexiCapture Cloud, customers must update their locally installed FlexiCapture client components to Release 4 Update 9. Customers using existing IMAP or GraphMail Image Import Profiles must also sign in to each affected profile again after completing the update.

Distributed (64-bit)

Download

Developer package only

Download

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request