KB5039212 and KB5039211 update causing problems in NiceLabel utilizzando internal fonts delle stampanti Honeywell.

Alberto Berti 20 Reputation points
2024-06-17T15:44:27.66+00:00

When I open a NiceLabel LBL file that uses texts with proprietary fonts from Honeywell printers, these objects are enormous in length and are not manageable. Removing the KB5039212 update makes the problem go away.

2024-06-17_17-37-20 No Update.jpg

2024-06-17_17-27-39

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,108 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,850 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 33,781 Reputation points Microsoft Vendor
    2024-06-18T01:02:39.2233333+00:00

    Hi Alberto Berti,

    Thank you for posting in Microsoft Q&A.

    Since the issue is caused by the update KB5039212, it is recommended to feedback to Microsoft. You can send feedback using the Feedback Hub app in Windows 10 and 11.

    Please refer to this link.

    https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.


2 additional answers

Sort by: Most helpful
  1. Alberto Berti 20 Reputation points
    2024-06-18T07:34:14.9666667+00:00

    We have encountered this issue on all our customers who use this configuration to manage our machinery in production. We have set up a test PC to carry out tests, we are at your complete disposal, for us it is vital to solve the problem. As per your advice we have activated procedures with Feedback Hub.


  2. Alberto Berti 20 Reputation points
    2024-07-11T09:58:27.53+00:00

    It appears that the July 9 cumulative update resolved the crash, we are still checking to see if our customers' issues have been resolved by this update.

    0 comments No comments