The following updates have proven to cause problems with receipts not appearing in the receipt journal.

December 2025 Windows security update (KB5071546, KB5071544, KB5071543)

ATTENTION! Completing the uninstallation of a KB update can in some cases take a very long time at reboot; over an hour. So if the store only has one cash register, do the uninstallation outside opening hours.
We've hade cases on windows 10 where it took over one hour at the startup after rebooting windows to finish the uninstallation of the KB.
The initial uninstallation in the "Uninstall windows updates" before reboot takes only around 5 minutes.

If a customer reports an issue in EGPOS related to: 
Receipts are not sent from the local POS to the central environment.
Receipts cannot be parked because they are not transferred to the master register (StoreCentral) for further processing.
Sales data is not transferred centrally, which means that reports are not updated.
End-of-day reports are not submitted.

How the issue presents in Lindbak POS Local.dbo.poslog: 
The state on the lastest receipts created says READYTOSEND. 

How the issue presents in LRSlog:

The LRSlog will say 'Unable to write POSLOG XML to MSMQ' this is an indication that MSMQ is effected by the windows update. 

Example SE: 
18.12.2025 11.44.09.678           Error  99  Exception occured: 'Unable to write POSLOG XML to MSMQ', System.Messaging.MessageQueueException: 'Det finns inte tillräckligt med resurser för att utföra åtgärden.'
Stack:
   vid System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)
   vid System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueTransaction transaction, MessageQueueTransactionType transactionType)
   vid System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueTransactionType transactionType)
   vid Lindbak.Kasse.DataLayer.ServiceAgents.Services.KasseJournalSA.MSMQJournal.SendMessageOnMSMQ(Message message, String label)
   vid Lindbak.Kasse.DataLayer.ServiceAgents.Services.KasseJournalSA.MSMQJournal.SaveJournal(String xml, Int64 receiptid, POSLogStatus status, Int32 version, String retailStoreId, String retailStoreIdLocal, Byte[] receiptAsPdf, List`1 signatures)

Example EN:

13.12.2025 00.00.23.669           Error     38  Exception occured: 'Unable to write POSLOG XML to MSMQ', System.Messaging.MessageQueueException: 'Insufficient resources to perform operation.'
Stack:
   at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)
   at System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueTransaction transaction, MessageQueueTransactionType transactionType)
   at System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueTransactionType transactionType)
   at Lindbak.Kasse.DataLayer.ServiceAgents.Services.KasseJournalSA.MSMQJournal.SendMessageOnMSMQ(Message message, String label)
   at Lindbak.Kasse.DataLayer.ServiceAgents.Services.KasseJournalSA.MSMQJournal.SaveJournal(String xml, Int64 receiptid, POSLogStatus status, Int32 version, String retailStoreId, String retailStoreIdLocal, Byte[] receiptAsPdf, List`1 signatures, Nullable`1 isSendingPOSLogBatchEnabled)

Command line command to check if any of the causing updates are installed

wmic qfe | findstr "KB5071546 KB5071544 KB5071543"

Fixes

Important - Pause Windows Updates

Windows Updates must remain paused on all affected registers until a confirmed workaround or fix is in place.

If updates are re-enabled, the issue may return, causing:

• Receipts not being sent

• Sales data not updating centrally

• End-of-day reports failing

Always pause Windows Updates again when the pause period expires if no workaround or fix has been implemented.

This is how you can uninstall the security update from the cash register.

1. Pause Windows update
   1. Open the Windows Update settings by clicking "Start / Settings / Update & Security". You will see the following window.
      
   2. Scroll down and click the "Advanced options"
       
   3. In the "Advanced options" screen, scroll down and select a date in the "Pause until" drop down. Choose a date that is as far in advance as possible, usually 35 days.
      
   4. Close the window. (It automatically saves your setting)
2. Uninstall the Windows update.
   1. Go to control panel and the following location "Control panel / Programs / Programs and features / Installed Updates".
   2. Find the correct update described above. In this instance KB5071546.
   3. Right click it and choose "Uninstall"
      
   4. Confirm by clicking "Yes" here.
      
   5. Wait until the installation is done…
      
   6. Confirm restart
      
3. When reboot is done please check that the Windows update has been uninstalled and that further updates have been paused.
4. Start EGPOS. 
5. The automatic cleanup job running every hour (or every 30 minutes in some cases) will do the processing of the receipts.
   It will just take some time before all receipts have been processed. 

Group Policy Editor on Windows 10

In some windows 10 environments the postponing 35 days option is not shown in the  Update & Security Advanced options.

Then Group Policy editor can be used to disable the updates. If this is used, the updates must be turned back on manually at a later time.

To disable windows update in group policy editor:

1. Press Windows key + R
2. type gpedit.msc, and press Enter to open the Local Group Policy Editor.
3. Navigate to: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
4. Double-click "Configure Automatic Updates".
5. Select "Disabled" to stop automatic downloads entirely
6. Click OK
7. A windows restart seems to be required to apply the setting.