NOW-proto worker has been terminated

Hello,

Thank you for the details and the log excerpt.

This error means RDM on your notebook lost its link to Devolutions Agent on the PAW, so every new jump in that RDP session fails.

To clear it, disconnect the RDP session to the PAW and connect again.

Since you are already on the latest versions, we would like to look into this with our development team.

Next time it happens, please send us the Agent logs from the PAW and the exact time of the error.

Please also let us know if the same account is ever connected to the PAW in more than one session.

Finally, does the error tend to appear after the session was idle, locked, or reconnected?

Best regards,

Hello,

Thank you for the details and the log excerpt.

This error means RDM on your notebook lost its link to Devolutions Agent on the PAW, so every new jump in that RDP session fails.

To clear it, disconnect the RDP session to the PAW and connect again.

Since you are already on the latest versions, we would like to look into this with our development team.

Next time it happens, please send us the Agent logs from the PAW and the exact time of the error.

Please also let us know if the same account is ever connected to the PAW in more than one session.

Finally, does the error tend to appear after the session was idle, locked, or reconnected?

Best regards,

Hey Carl @Carl Marien

sure i will provide the log if the error happens to appear again.

I use multiple Jump Sessions via the same PAW but never open multiple session to the paw from my notebook.

Honestly i cant exactly pin point when it happens but i would say it happens after unlocking my windows session or after a idle period of rdm.

I dont know if it matters, but we use Yubikeys for Login to the Notebook and the PAW.

Best regards,

Moritz Heppert

Hello Moritz,

Thank you for the details, I’ve passed them to our development team, who are already working on Agent connection stability, and your case is now part of that work.

Until there’s a fix, disconnecting and reconnecting the RDP session to the PAW will clear the error.

The next time it happens, please send us the Devolutions Agent logs from the PAW, the exact time of the error, and the Agent version installed on the PAW.

Best regards,

Hello,

Thank you for the additional details and the log screenshot.

The log shows that the Devolutions Agent on your PAW is version 2026.1.0. A fix for the “NOW-proto worker has been terminated” error was released in Devolutions Agent 2026.2.4. Please update the Agent on the PAW to the latest version, then disconnect and reconnect the RDP session from your notebook to the PAW.

If the error comes back after the update, please send us:

1. The exact time it happened

2. The Devolutions Agent logs from the PAW (these are separate from the Remote Desktop Manager logs)

3. Whether the same user had more than one RDP session open to the PAW at that time

In the meantime, disconnecting and reconnecting the RDP session to the PAW should clear the error when it appears.

Best regards,

Hello,

Thank you for the additional details and the log screenshot.

The log shows that the Devolutions Agent on your PAW is version 2026.1.0. A fix for the “NOW-proto worker has been terminated” error was released in Devolutions Agent 2026.2.4. Please update the Agent on the PAW to the latest version, then disconnect and reconnect the RDP session from your notebook to the PAW.

If the error comes back after the update, please send us:

1. The exact time it happened

2. The Devolutions Agent logs from the PAW (these are separate from the Remote Desktop Manager logs)

3. Whether the same user had more than one RDP session open to the PAW at that time

In the meantime, disconnecting and reconnecting the RDP session to the PAW should clear the error when it appears.

Best regards,

Hey @Carl Marien,

thank you for your reply. Actually the PAW has no internet connection so maybe thats why i didnt received any notice about an avaible update for the devolutions Agent. I just installed Version 2026.3.1 and reconnected the rdp session. I will report back if the issue persists.

Best Regards

Hello,

All right, thanks for the update. Please let me know if the issue persists after the update.

best regard

Actually the same error occured again at 11:32.35.

Devolutions.NowClient.NowClientException: NOW-proto worker has been terminated.

at Devolutions.NowClient.NowClient.ThrowIfWorkerTerminated()

at Devolutions.NowClient.NowClient.SetRdmAppNotifyHandler(RdmAppNotifyHandler handler)

at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.SetRdmAppNotifyHandler(RdmAppNotifyHandler handler)

at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.StartAndWaitForRdmReady(Int32 timeoutSeconds, CancellationToken cancellationToken)

at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.Jump(Connection targetConnection, JumpedConnectionResult jumpedConnectionResult)

Devolutions Agent is at Version 20263.1.0

RDM is 2026.3.15.0 on both stations.

Could it be related to switchting the network connection?

Hello

We have some changes coming in the next release (2026.3.16) that should make the client to agent connection much more robust. Once that is available and you've updated your (client side) RDM, please let me know if you're still experiencing issues.

Thanks for your patience, and kind regards

Hello

RDM Windows 2026.3.16 is now available and contains improvements for the rendezvous between RDM and the Agent. I'd appreciate if you can update RDM on the client to the latest version, ensure you are running a recent RDM 2026.3 on the jump host and preferably use the latest Agent version (2026.3.3.0 at this time).

Please let me know if things are improved or you are still experiencing issues.

Thanks and kind regards,