An issue with the default OCR engine has been detected and causing the stopping of the OCR process and consequently also the crashing of the Processing Service.

The issue can be identified with the stopping of the Process Service at the log line "Finalizing document..." and an entry in the Windows Events Viewer with an exception inside the Windows module ntdll.

The issue is originating starting of Microsoft Update KB4041686 which has been rolled up in several different cumulative updates for each Windows version as per follow:

 

Windows 10 Version 1607 - KB4056890

Windows 10 Version 1703 - KB4056891

Windows 10 Version 1709, Windows Server 2016 - KB4056892

Windows 10 Version 1709, Windows Server 2016 - KB4058702

Windows 8.1, Windows Server 2012 R2 Service Pack 1 - KB4056895

Windows Server 2012 R2 Service Pack 1 - KB4056896

Windows Server 2008 R2 Service Pack 1, Windows 7 Service Pack 1 - KB4056897

Windows 8.1, Windows Server 2012 R2 Standard - KB4056898

Windows Server 2012 Standard - KB4056899

 

Microsoft resolved the issue with the most recent updates as per follow:

 

Windows 10 Version 1607 - KB4057142

Windows 10 Version 1703 - KB4057144

Windows 10 Version 1709, Windows Server 2016  - KB4058258

Windows 8.1 - KB4057401

Windows Server 2012 R2 Standard - KB4057401

Windows Server 2012 Standard - KB4057402

Windows Server 2008 R2 Service Pack 1 - KB4057400

Windows 7 Service Pack 1 - KB4057400

 

The resolving updates may not be listed as automatic updates so it is suggested to manually check the available updates including the optional ones.

Please note that the issue may still be present also after installing the mentioned updates because the original KB, producing the problem, is rolled-up in different cumulative's as well and they may also differ by system locale.

The issue follows the following updates history for Windows 7 and Windows 2008 systems:

 

KB4041686 (originating the problem) -> included in KB4048957 -> included in KB4051034 -> included in KB4054518 -> included in KB4056894 -> included in KB4057400 -> included in KB4074598 -> included in KB4075211 -> included in KB4088875 -> included in KB4088881 -> included in KB4093118 -> included in KB4093113

 

and the following update history for Windows 8 and Windows 2012 systems:

 

KB4041685 (originating the problem) -> included in KB4048958 -> included in KB4050946 -> included in KB4054519 -> included in KB4056895 -> included in KB4057401 -> included in KB4074594 -> included in KB4075212 -> included in KB4088876 -> included in KB4088882 -> included in KB4093114 -> included in KB4093121

 

*UPDATE*: The issue has been definitely solved with a patch also for the cases where it was still present after installing the resolving Microsoft updates. The patch is now available for all brands in all internal builds starting of v4.8.0.11 and it will rolled-up in the next official release v4.9.