[GH-ISSUE #213] Sometimes you cant start connection until restart

kerem commented

2026-02-28 12:02:20 +03:00

Owner

Originally created by @majkinetor on GitHub (Feb 28, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/213

Originally assigned to: @VShawn on GitHub.

It happened 3 times since yesterday that I can't start a connection, it just does nothing in both launcher and the list. After the restart, it works.

Originally created by @majkinetor on GitHub (Feb 28, 2022). Original GitHub issue: https://github.com/1Remote/1Remote/issues/213 Originally assigned to: @VShawn on GitHub. It happened 3 times since yesterday that I can't start a connection, it just does nothing in both launcher and the list. After the restart, it works.

kerem

2026-02-28 12:02:20 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Mar 2, 2022):

close by github.com/VShawn/PRemoteM@6fa1fcb49a

@VShawn commented on GitHub (Mar 2, 2022): close by https://github.com/VShawn/PRemoteM/commit/6fa1fcb49a0b0e5fb9d5e3c07d8d7ab710a6ade8

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Apr 2, 2022):

Still happens with 0.6.2.1. Not sure when it happens, I know it happened each time when I was doing some config editing and/or duplicating. I am having trouble reproducing it, but once it happens you need to restart PRM.

@majkinetor commented on GitHub (Apr 2, 2022): Still happens with 0.6.2.1. Not sure when it happens, I know it happened each time when I was doing some config editing and/or duplicating. I am having trouble reproducing it, but once it happens you need to restart PRM.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Apr 18, 2022):

I am having hard time troubleshooting this. When it happens, and I delete logs before trying connection, this is the only thing that shows when I use launcher:

2022-04-18T21:40:51.5272722+02:00[ThreadId:0000000001]		Debug		Call shortcut to invoke launcher _isHidden = True
2022-04-18T21:40:51.5322590+02:00[ThreadId:0000000001]		Debug		Launcher resize:  w = 400, h = 366
2022-04-18T21:40:52.0180296+02:00[ThreadId:0000000001]		Debug		Call HideMe()
2022-04-18T21:40:52.0200281+02:00[ThreadId:0000000001]		Debug		Call HideMe()
2022-04-18T21:40:52.0210280+02:00[ThreadId:0000000001]		Debug		SetSelfStartingHelper.SetSelfStartByRegistryKey(True, "PRemoteM")
2022-04-18T21:40:52.3225347+02:00[ThreadId:0000000001]		Debug		Launcher resize:  w = 400, h = 366

Anything I can do to identify the reason besides turning development environment up? Perhaps you can enrich logs regarding this?

It does seem to have something to do with reconnecting after idle period. When I restart the app and try connecting to local server, I get immediately reconnect screen which is strange, since I just restarted PRM:

If I click Reconnect it connects normally.

@majkinetor commented on GitHub (Apr 18, 2022): I am having hard time troubleshooting this. When it happens, and I delete logs before trying connection, this is the only thing that shows when I use launcher: ``` 2022-04-18T21:40:51.5272722+02:00[ThreadId:0000000001] Debug Call shortcut to invoke launcher _isHidden = True 2022-04-18T21:40:51.5322590+02:00[ThreadId:0000000001] Debug Launcher resize: w = 400, h = 366 2022-04-18T21:40:52.0180296+02:00[ThreadId:0000000001] Debug Call HideMe() 2022-04-18T21:40:52.0200281+02:00[ThreadId:0000000001] Debug Call HideMe() 2022-04-18T21:40:52.0210280+02:00[ThreadId:0000000001] Debug SetSelfStartingHelper.SetSelfStartByRegistryKey(True, "PRemoteM") 2022-04-18T21:40:52.3225347+02:00[ThreadId:0000000001] Debug Launcher resize: w = 400, h = 366 ``` Anything I can do to identify the reason besides turning development environment up? Perhaps you can enrich logs regarding this? It does seem to have something to do with reconnecting after idle period. When I restart the app and try connecting to local server, I get immediately reconnect screen which is strange, since I just restarted PRM: ![image](https://user-images.githubusercontent.com/85767/163866986-50d2c8cf-0896-4121-b25f-e7fd6a60017c.png) If I click Reconnect it connects normally.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 19, 2022):

sorry I didn't notice the reopened ticket.

I dont know why it never happen to me.

But when next time it happens, you can

And you will get a consol window.

Then try start a connection with nothing happen, PRM will print log on the consol, just show me the log : )

@VShawn commented on GitHub (Apr 19, 2022): sorry I didn't notice the reopened ticket. I dont know why it never happen to me. But when next time it happens, you can ![image](https://user-images.githubusercontent.com/10143738/163897929-a574c766-24b3-4f86-a120-9d98e1d6514a.png) And you will get a consol window. Then try start a connection with nothing happen, PRM will print log on the consol, just show me the log : )

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 19, 2022):

It does seem to have something to do with reconnecting after idle period. When I restart the app and try connecting to local server, I get immediately reconnect screen which is strange, since I just restarted PRM:

Based on the information you gave, maybe there some error during the initialization, it sotp the connection initialization( and the remote window init) but not be thrown.

Then the un-init RDP connection will be remembered by the RemoteWindowPool and your next connecte command will be rejected by:

https://github.com/VShawn/PRemoteM/blob/dev/PRemoteM/Model/RemoteWindowPool.cs#L304-L306

That's my reasoning

@VShawn commented on GitHub (Apr 19, 2022): > It does seem to have something to do with reconnecting after idle period. When I restart the app and try connecting to local server, I get immediately reconnect screen which is strange, since I just restarted PRM: Based on the information you gave, maybe there some error during the initialization, it sotp the connection initialization( and the remote window init) but not be thrown. Then the un-init RDP connection will be remembered by the RemoteWindowPool and your next connecte command will be rejected by: https://github.com/VShawn/PRemoteM/blob/dev/PRemoteM/Model/RemoteWindowPool.cs#L304-L306 That's my reasoning

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Apr 19, 2022):

Regarding Support clicking window, it looks like this console provides the same logs as those in the .md logs ?

@majkinetor commented on GitHub (Apr 19, 2022): Regarding Support clicking window, it looks like this console provides the same logs as those in the .md logs ?

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Apr 23, 2022):

I found out that just one connection cant be started. Others worked. After the restart, it resolved.

@majkinetor commented on GitHub (Apr 23, 2022): I found out that just one connection cant be started. Others worked. After the restart, it resolved. <details> ![prm](https://user-images.githubusercontent.com/85767/164946020-220a80a1-3de1-41e4-9c4f-3f166297d9c8.gif) </details>

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 24, 2022):

I‘ve made a SessionControlService.cs instead of RemoteWindowPool.cs yesterday, I think it would fix this.

https://github.com/VShawn/PRemoteM/blob/dev_net6/Ui/Service/SessionControlService.cs

@VShawn commented on GitHub (Apr 24, 2022): I‘ve made a SessionControlService.cs instead of RemoteWindowPool.cs yesterday, I think it would fix this. https://github.com/VShawn/PRemoteM/blob/dev_net6/Ui/Service/SessionControlService.cs

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@stetze commented on GitHub (Jul 13, 2022):

After Installation of 0.7.0 it's More worse then before. Only a restart of the Software helps. 😔

@stetze commented on GitHub (Jul 13, 2022): After Installation of 0.7.0 it's More worse then before. Only a restart of the Software helps. 😔

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 14, 2022):

After Installation of 0.7.0 it's More worse then before. Only a restart of the Software helps. 😔

That's awful.

Worse, I couldn't reproduce the problem so that I can't locate how the bug cause.

===

@majkinetor Do you still MEET this BUG?

@VShawn commented on GitHub (Jul 14, 2022): > After Installation of 0.7.0 it's More worse then before. Only a restart of the Software helps. 😔 That's awful. Worse, I couldn't reproduce the problem so that I can't locate how the bug cause. === @majkinetor Do you still MEET this BUG?

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@stetze commented on GitHub (Jul 14, 2022):

My workmate have the Same Problems. We Both use Windows 11 pro and the Store Version.

I can't work with this versions. I Must downgrade to the Old Version.

@stetze commented on GitHub (Jul 14, 2022): My workmate have the Same Problems. We Both use Windows 11 pro and the Store Version. I can't work with this versions. I Must downgrade to the Old Version.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 14, 2022):

My workmate have the Same Problems. We Both use Windows 11 pro and the Store Version.

I don't have a win11 installed on my pc, so PRemoteM are not been fully tested on Win11. Only the portable exe been tested on a virtual machine win11.

You can sharing me the log when you meet the bug, may be we can find something in the logs.

@VShawn commented on GitHub (Jul 14, 2022): > My workmate have the Same Problems. We Both use Windows 11 pro and the Store Version. I don't have a win11 installed on my pc, so PRemoteM are not been fully tested on Win11. Only the portable exe been tested on a virtual machine win11. You can sharing me the log when you meet the bug, may be we can find something in the logs.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Jul 14, 2022):

I think I still have it but its rare. Using w10. Not using store.

@majkinetor commented on GitHub (Jul 14, 2022): I think I still have it but its rare. Using w10. Not using store.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@stetze commented on GitHub (Jul 14, 2022):

With the github zip Version 0.6.2 it's much better. I Try tomorrow the 0.7 zip Version. Maybe it Makes an Difference against the Store Version.

@stetze commented on GitHub (Jul 14, 2022): With the github zip Version 0.6.2 it's much better. I Try tomorrow the 0.7 zip Version. Maybe it Makes an Difference against the Store Version.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@ndd200 commented on GitHub (Jul 18, 2022):

我有同样的问题。
于是我装了Github版便携模式，商店版配置存appdata。两个版本用同一个PRemoteM.db。对比两边的json配置，几乎是一样的，但是商店版打开某几个远程就是看着像连上了，在调整分辨率的时候闪退了，重启程序也无法解决。
本来还想仔细研究的，在反复重启的过程中，两个版本又都不闪退了。

———————割一下———————
现在大致可以确认，有问题的是商店版。
商店版连接某几台服务器时候，会闪一下退出连接。同一时间，关商店版，启动Git版没问题。然后再关Git版，启动商店版就闪退。
两个版本的Locality.json和PRemoteM.json配置是一致的，尤其是分辨率完全一样。

日志里错误都是error code 4360。

[T:001][10:59:57.069] Debug RDP Host: RdpOnDisconnected
[T:001][10:59:57.070] Debug AxMsRdpClient09Host: Status => Disconnected
[T:001][10:59:57.071] Warning [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:102)] RDP(blablabla) exit with error code 4360(未能重新连接到远程会话。
请重新尝试连接。)
[T:001][10:59:57.554] Debug RDP Host: _rdpClient.Dispose()
[T:019][10:59:57.558] Debug MarkProtocolHostToClose: marking to close: AxMsRdpClient09Host(id = 40, hash = 13273752)
[T:019][10:59:57.559] Debug Current: Host = 0, Full = 0, Tab = 1, HostToBeDispose = 1
[T:019][10:59:57.562] Debug CloseEmptyWindows: closing tab(16355056)
[T:019][10:59:57.563] Info CloseEmptyWindows: Current: Host = 0, Full = 0, Tab = 0, HostToBeDispose = 1, WindowToBeDispose = 1
[T:019][10:59:57.563] Warning [SessionControlService.cs(b__0:535)] CloseEmptyWindows: 1 Empty Host closed
[T:019][10:59:57.565] Debug Closing: 1 Empty Host.
[T:019][10:59:57.566] Info CloseMarkedProtocolHost: Current: Host = 0, Full = 0, Tab = 0, HostToBeDispose = 0
[T:001][10:59:57.595] Debug RDP Host: _rdpClient.Dispose()

@ndd200 commented on GitHub (Jul 18, 2022): 我有同样的问题。于是我装了Github版便携模式，商店版配置存appdata。两个版本用同一个PRemoteM.db。对比两边的json配置，几乎是一样的，但是商店版打开某几个远程就是看着像连上了，在调整分辨率的时候闪退了，重启程序也无法解决。本来还想仔细研究的，在反复重启的过程中，两个版本又都不闪退了。 ———————割一下——————— 现在大致可以确认，有问题的是商店版。商店版连接某几台服务器时候，会闪一下退出连接。同一时间，关商店版，启动Git版没问题。然后再关Git版，启动商店版就闪退。两个版本的Locality.json和PRemoteM.json配置是一致的，尤其是分辨率完全一样。日志里错误都是error code 4360。 [T:001][10:59:57.069] `Debug` RDP Host: RdpOnDisconnected [T:001][10:59:57.070] `Debug` AxMsRdpClient09Host: Status => Disconnected [T:001][10:59:57.071] `Warning` [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:102)] RDP(blablabla) exit with error code 4360(未能重新连接到远程会话。请重新尝试连接。) [T:001][10:59:57.554] `Debug` RDP Host: _rdpClient.Dispose() [T:019][10:59:57.558] `Debug` MarkProtocolHostToClose: marking to close: AxMsRdpClient09Host(id = 40, hash = 13273752) [T:019][10:59:57.559] `Debug` Current: Host = 0, Full = 0, Tab = 1, HostToBeDispose = 1 [T:019][10:59:57.562] `Debug` CloseEmptyWindows: closing tab(16355056) [T:019][10:59:57.563] `Info` CloseEmptyWindows: Current: Host = 0, Full = 0, Tab = 0, HostToBeDispose = 1, WindowToBeDispose = 1 [T:019][10:59:57.563] `Warning` [SessionControlService.cs(<CloseProtocolHostAsync>b__0:535)] CloseEmptyWindows: 1 Empty Host closed [T:019][10:59:57.565] `Debug` Closing: 1 Empty Host. [T:019][10:59:57.566] `Info` CloseMarkedProtocolHost: Current: Host = 0, Full = 0, Tab = 0, HostToBeDispose = 0 [T:001][10:59:57.595] `Debug` RDP Host: _rdpClient.Dispose()

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@meyomey commented on GitHub (Jul 20, 2022):

Hi VShawn, with the Store version (0.7.0) I can currently only create one connection. No improvement even after a restart. With the Github version everything is ok. (both runs under win10)

@meyomey commented on GitHub (Jul 20, 2022): Hi VShawn, with the Store version (0.7.0) I can currently only create one connection. No improvement even after a restart. With the Github version everything is ok. (both runs under win10)

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 21, 2022):

Hi VShawn, with the Store version (0.7.0) I can currently only create one connection. No improvement even after a restart. With the Github version everything is ok. (both runs under win10)

@meyomey Can you provide the running log of store version after reproduct the bug? I can figure out what's happening with the log.

@VShawn commented on GitHub (Jul 21, 2022): > Hi VShawn, with the Store version (0.7.0) I can currently only create one connection. No improvement even after a restart. With the Github version everything is ok. (both runs under win10) @meyomey Can you provide the running log of store version after reproduct the bug? I can figure out what's happening with the log.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@meyomey commented on GitHub (Jul 21, 2022):

How do I start the console? Right-click three times on Support unfortunately doesn't work.

@meyomey commented on GitHub (Jul 21, 2022): How do I start the console? Right-click three times on Support unfortunately doesn't work.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@chrisonline commented on GitHub (Jul 21, 2022):

Same problem here on Windows 11 and Store version.
I can connect to one server. If I want to connect to a second server, it opens and closes immediately.

@chrisonline commented on GitHub (Jul 21, 2022): Same problem here on Windows 11 and Store version. I can connect to one server. If I want to connect to a second server, it opens and closes immediately.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 22, 2022):

@meyomey,@chrisonline you can create the path C:\Users\<YOUR NAME>\AppData\Roaming\PRemoteM\Logs\ manually.

Then reproduct the bug again. The log file would be present.

As far as I known, most error would be

RDP exit with error code 4360

The erro code should not relate to PRemoteM’s control logic.

though I can not find the meaning of error code 4360,

@VShawn commented on GitHub (Jul 22, 2022): ![image](https://user-images.githubusercontent.com/10143738/180378916-82590f8f-606b-453e-8665-b1fa178da95c.png) @meyomey,@chrisonline you can create the path `C:\Users\<YOUR NAME>\AppData\Roaming\PRemoteM\Logs\` manually. Then reproduct the bug again. The log file would be present. ![image](https://user-images.githubusercontent.com/10143738/180377958-cbb6cd9f-9041-4a35-9a18-2d887b704bd1.png) --- As far as I known, most error would be ``` RDP exit with error code 4360 ``` The erro code should not relate to PRemoteM’s control logic. though I can not find the meaning of error code 4360, ![](https://user-images.githubusercontent.com/10143738/179505037-3d0e9537-e1c4-46c3-8860-d467e72bb0a9.png)

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 22, 2022):

found a same ticket here: https://forum.asg-rd.com/showthread.php?tid=11016

As this guy said

I'm sorry to hear that. Right now it's not clear what could cause those issues only on some installations. 
As my colleague stated we didn't change anything related to RDP in patch3. 
So first we need time to be able to reproduce the problem on our side and 
also this month is affected by vacation so things generally need a bit 
more time. If you extended your license then you will be able use the next patches as well.

I didn't change anything related to RDP in 0.7.0.

@VShawn commented on GitHub (Jul 22, 2022): found a same ticket here: https://forum.asg-rd.com/showthread.php?tid=11016 As this guy said ``` I'm sorry to hear that. Right now it's not clear what could cause those issues only on some installations. As my colleague stated we didn't change anything related to RDP in patch3. So first we need time to be able to reproduce the problem on our side and also this month is affected by vacation so things generally need a bit more time. If you extended your license then you will be able use the next patches as well. ``` I didn't change anything related to RDP in 0.7.0.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@chrisonline commented on GitHub (Jul 22, 2022):

Hi @VShawn !

Attached is the log file with the error message:
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.

What I did:
Open RDP Session to Server 1 and the session is still running
Now try to open RDP Session to Server 2 and it seems it is connection. I see very short the blue RDP tab and it closes afterwards.

PRemoteM.log_20220722.md
.

@chrisonline commented on GitHub (Jul 22, 2022): Hi @VShawn ! Attached is the log file with the error message: System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. What I did: Open RDP Session to Server 1 and the session is still running Now try to open RDP Session to Server 2 and it seems it is connection. I see very short the blue RDP tab and it closes afterwards. [PRemoteM.log_20220722.md](https://github.com/1Remote/PRemoteM/files/9165692/PRemoteM.log_20220722.md) .

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@majkinetor commented on GitHub (Jul 22, 2022):

It looks like we have 2 similar problems here. In my original report on selection nothing happens at all.

@majkinetor commented on GitHub (Jul 22, 2022): It looks like we have 2 similar problems here. In my original report on selection nothing happens at all.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 22, 2022):

@chrisonline

Hi thanks for your log. Accroding to the log the error was:

[T:001][09:34:59.509]	`Warning`		[AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)]	RDP(XXXXX) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen.
Wiederholen Sie den Verbindungsversuch.)

@VShawn commented on GitHub (Jul 22, 2022): @chrisonline Hi thanks for your log. Accroding to the log the error was: ``` [T:001][09:34:59.509] `Warning` [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)] RDP(XXXXX) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen. Wiederholen Sie den Verbindungsversuch.) ```

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 22, 2022):

It looks like we have 2 similar problems here. In my original report on selection nothing happens at all.

You are right. One is because of the mess control logic in the SessionControlService (the original one you report). In this case, the session will not be opened.

The other one is happen in the store version which I can't not locate where the bug is.(RDP exit with error code 4360.) In this case, the session opens and closes immediately.

@VShawn commented on GitHub (Jul 22, 2022): > It looks like we have 2 similar problems here. In my original report on selection nothing happens at all. You are right. One is because of the mess control logic in the `SessionControlService` (the original one you report). In this case, the session will not be opened. The other one is happen in the store version which I can't not locate where the bug is.(RDP exit with error code 4360.) In this case, the session opens and closes immediately.

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@stetze commented on GitHub (Jul 22, 2022):

@chrisonline

Hi thanks for your log. Accroding to the log the error was:


[T:001][09:34:59.509]	`Warning`		[AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)]	RDP(XXXXX) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen.

Wiederholen Sie den Verbindungsversuch.)

I have the Same error on my Store Version 0.7.0 with Windows 11 Pro (German).

@stetze commented on GitHub (Jul 22, 2022): > @chrisonline > > > > Hi thanks for your log. Accroding to the log the error was: > > > > ``` > > [T:001][09:34:59.509] `Warning` [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)] RDP(XXXXX) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen. > > Wiederholen Sie den Verbindungsversuch.) > > > > ``` > > I have the Same error on my Store Version 0.7.0 with Windows 11 Pro (German).

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@chrisonline commented on GitHub (Jul 22, 2022):

FYI

I use also the latest Store Version on Windows 11 (German).

@chrisonline commented on GitHub (Jul 22, 2022): FYI I use also the latest Store Version on Windows 11 (German).

kerem commented

2026-02-28 12:02:21 +03:00

Author

Owner

@meyomey commented on GitHub (Jul 22, 2022):

as an addition from me (Store Version):

[T:001][13:56:39.244] Warning [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)] RDP(73 - MBT-73) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen.
Wiederholen Sie den Verbindungsversuch.)

@meyomey commented on GitHub (Jul 22, 2022): as an addition from me (Store Version): > [T:001][13:56:39.244] `Warning` [AxMsRdpClient09Host.cs(OnRdpClientDisconnected:103)] RDP(73 - MBT-73) exit with error code 4360(Das Wiederherstellen der Verbindung mit der Remotesitzung ist fehlgeschlagen. Wiederholen Sie den Verbindungsversuch.)

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 23, 2022):

0.7.1.1 is in publish processing, and this patch may fix rdp error code 4360

tested in my store beta test group, no more 4360 reproduce

Please help me test this build, it will be published after a certification(up to 3 business days).

@VShawn commented on GitHub (Jul 23, 2022): 0.7.1.1 is in publish processing, and this patch may fix `rdp error code 4360` ![image](https://user-images.githubusercontent.com/10143738/180588603-256f92f4-27da-4b3e-9ff5-78907a5dec24.png) tested in my store beta test group, no more 4360 reproduce ![image](https://user-images.githubusercontent.com/10143738/180588714-25608548-096c-47f8-8384-6fbee497bbca.png) Please help me test this build, it will be published after a certification(up to 3 business days). ![image](https://user-images.githubusercontent.com/10143738/180588676-6e7b10c7-afeb-4124-ab41-8b1b1110a2ab.png)

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@stetze commented on GitHub (Jul 24, 2022):

0.7.1.1 is in publish processing, and this patch may fix rdp error code 4360

tested in my store beta test group, no more 4360 reproduce

Please help me test this build, it will be published after a certification(up to 3 business days).

I think it's fixed. More Tests tomorrow at work.

Edit: Sorry it's Not Working. The Problem still exist.

@stetze commented on GitHub (Jul 24, 2022): > 0.7.1.1 is in publish processing, and this patch may fix `rdp error code 4360` > > > > ![image](https://user-images.githubusercontent.com/10143738/180588603-256f92f4-27da-4b3e-9ff5-78907a5dec24.png) > > > > tested in my store beta test group, no more 4360 reproduce > > > > ![image](https://user-images.githubusercontent.com/10143738/180588714-25608548-096c-47f8-8384-6fbee497bbca.png) > > > > > > > > Please help me test this build, it will be published after a certification(up to 3 business days). > > > > ![image](https://user-images.githubusercontent.com/10143738/180588676-6e7b10c7-afeb-4124-ab41-8b1b1110a2ab.png) > > I think it's fixed. More Tests tomorrow at work. Edit: Sorry it's Not Working. The Problem still exist.

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 25, 2022):

@stetze88 sorry but the fix patch(0.7.1.1) has not been certificated yet, it still in the certification queue of Microsoft store.

@VShawn commented on GitHub (Jul 25, 2022): @stetze88 sorry but the fix patch(0.7.1.1) has not been certificated yet, it still in the certification queue of Microsoft store.

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 26, 2022):

hey guys, 0.7.1.1 is available in the store now :)

@VShawn commented on GitHub (Jul 26, 2022): hey guys, 0.7.1.1 is available in the store now :)

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@meyomey commented on GitHub (Jul 26, 2022):

Hi vshawn,
just tested the new store version at work. Works fine again. Thanks a lot!
And of course for your quick response.

@meyomey commented on GitHub (Jul 26, 2022): Hi vshawn, just tested the new store version at work. Works fine again. Thanks a lot! And of course for your quick response.

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@stetze commented on GitHub (Jul 26, 2022):

It's much better. But the Problem still Exists after a Long time of using.

@stetze commented on GitHub (Jul 26, 2022): It's much better. But the Problem still Exists after a Long time of using.

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 27, 2022):

It's much better. But the Problem still Exists after a Long time of using.

desponding. can you check the log? is it still rdp error code 4360?

@VShawn commented on GitHub (Jul 27, 2022): > It's much better. But the Problem still Exists after a Long time of using. desponding. can you check the log? is it still rdp error code 4360?

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@meyomey commented on GitHub (Jul 27, 2022):

Hi VShawn, today the connection was interrupted after half an hour and the programme was partially blocked. Unfortunately, error 4360 appears again in the log file....

PRemoteM.log_20220727.md

@meyomey commented on GitHub (Jul 27, 2022): Hi VShawn, today the connection was interrupted after half an hour and the programme was partially blocked. Unfortunately, error 4360 appears again in the log file.... [PRemoteM.log_20220727.md](https://github.com/1Remote/PRemoteM/files/9196462/PRemoteM.log_20220727.md)

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Jul 28, 2022):

Hi VShawn, today the connection was interrupted after half an hour and the programme was partially blocked. Unfortunately, error 4360 appears again in the log file....

Damn this bug :(

Maybe I should revert and leave store version at 0.6.X.

Anyway thanks for your testing.

@VShawn commented on GitHub (Jul 28, 2022): > Hi VShawn, today the connection was interrupted after half an hour and the programme was partially blocked. Unfortunately, error 4360 appears again in the log file.... Damn this bug :( Maybe I should revert and leave store version at 0.6.X. Anyway thanks for your testing.

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@chrisonline commented on GitHub (Jul 28, 2022):

For me, it is working fine so far. :-)
Thanks!

@chrisonline commented on GitHub (Jul 28, 2022): For me, it is working fine so far. :-) Thanks!

kerem commented

2026-02-28 12:02:22 +03:00

Author

Owner

@VShawn commented on GitHub (Sep 14, 2022):

by #263 and this ticket, seems it is working now.

@VShawn commented on GitHub (Sep 14, 2022): by #263 and this ticket, seems it is working now.

Rows
Columns

[GH-ISSUE #213] Sometimes you cant start connection until restart #1146