Support
Authorization

Newsletter

  Settings

Radmin 3.5 stopped working after Windows 10 update

 

Search  Rules 
Close
Login::
Password::
Forgot your password?
Register
Login
 
Pages: 1
Radmin 3.5 stopped working after Windows 10 update
 
After a recent security update of Windows 10 to:

OS Name: Microsoft Windows 10
HomeOS Version: 10.0.15063 N/A Build 15063

im having issues viewing remote desktop since the newest update.

i've already read a lot on the forum, tried some of the solutions that found here and there.

first of all i've tried to uninstall whole app, deleted registry entries, flushed driver cache, then reinstall again with no succes, Is there any know issue with newest build of windows 10?

the point is that ive a company computers running radmin server, with no problems till now, and i'm going on a vacation and its absolutely neccesary for me to have radmin working again by the end of the week ...
 
I have encountered this problem
 
Quote
adslcaiwrote:
I have encountered this problem

found a solution?
 
Same here. 7 of 10 of our computers that updated last night are getting the same thing. The 3 on the previous build are still functioning.
 
I have same problem.
Terminal mode, Transfer mode and reboot-restart mode is working.

my Radm_log is below.
Code
RServer3 2017.06.27 09:50 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.27 10:02  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.27 15:26 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.27 15:35  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.28 09:46 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.28 09:57  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.28 12:31 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.28 12:36  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.28 16:49 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.28 16:56  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.28 18:13 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.28 18:16  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:18 Radmin Server 3 is started
RServer3 2017.06.29 02:22 Radmin Server 3 is started
RServer3 2017.06.29 02:30 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 02:30 ThreadProc::WaitForMirrorState(REQ) failed
RServer3 2017.06.29 02:30 ThreadProc::WaitForMirrorState(ON) failed
RServer3 2017.06.29 02:31 Connection from  My-Server01 (192.168.1.1) (My-Name): Shutdown connection
RServer3 2017.06.29 02:31  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:31  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:32 Radmin Server 3 is started
RServer3 2017.06.29 02:32 Connection from  My-Server01 (192.168.1.1) (My-Name): Shutdown connection
RServer3 2017.06.29 02:32  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:32 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 02:32 ThreadProc::WaitForMirrorState(REQ) failed
RServer3 2017.06.29 02:32 ThreadProc::WaitForMirrorState(ON) failed
RServer3 2017.06.29 02:32 Connection from  My-Server01 (192.168.1.1) (My-Name): Shutdown connection
RServer3 2017.06.29 02:32  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:32  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 02:33 Radmin Server 3 is started
RServer3 2017.06.29 03:03 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 03:03 ThreadProc::WaitForMirrorState(REQ) failed
RServer3 2017.06.29 03:04 ThreadProc::WaitForMirrorState(ON) failed
RServer3 2017.06.29 03:10 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 09:07  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 09:07  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 09:07 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 09:07 ThreadProc::WaitForMirrorState(REQ) failed
RServer3 2017.06.29 09:07 ThreadProc::WaitForMirrorState(ON) failed
RServer3 2017.06.29 09:07 Connection from  My-Server01 (192.168.1.1) (My-Name): Shutdown connection
RServer3 2017.06.29 09:07  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 09:07  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 10:18 Connection from  My-Server01 (192.168.1.1) (My-Name): Shutdown connection
RServer3 2017.06.29 10:18  My-Server01 (192.168.1.1) connection closed
RServer3 2017.06.29 10:19 Connection from  My-Server01 (192.168.1.1) (My-Name): Remote Screen connection
RServer3 2017.06.29 10:19 ThreadProc::WaitForMirrorState(REQ) failed
RServer3 2017.06.29 10:19 ThreadProc::WaitForMirrorState(ON) failed
RServer3 2017.06.29 10:38  My-Server01 (192.168.1.1) connection closed
 
We had the same issue at my company. After trying all other solutions, the only thing that worked was to uninstall the latest Win 10 update (KB4022716).
 
I've run into the same issue on two Windows 10 Pro 64-bit computers after installing patch KB4022716 (2017-06 Cumulative Update).
Tried uninstalling and re-installing Radmin server.
I also noticed there is no longer a "C:\Windows\System32\rserver30" folder. Before or after re-installing Radmin.
 
we see the same and we believe its the same with 3.4.

KB4022716 (2017-06 Cumulative Update) breaks radmin server 3.5.
all looks in the connection log but in face the viewer doesnt render a picture.

is it by design, bug or else? is it going to be fixed in another windows 10 cumulative update?

please look into it - as you write you are win10 compatible - in fact radmin is broken now.
 
Same Problem here....

Has anybody found a workaround yet?

I really don't want to Roll back 15 PC's!
 
Hello,

New Windows update has affected Radmin. We are currently working on a solution. But for now the only way to make it work again is by uninstalling this new update. This can be done by going to Control Panel - Programs and Features - Choosing in the left panel - View installed updates – finding out last update and uninstalling it.
 
Same here, so Radmin is not W10 compatible at this moment :-{{
Edited: chromazone - 05.07.2017 07:01:19
 
Hello,

New Radmin server file has been made and is currently available on our website - [URL=http://www.radmin.com/download/index.php]http://www.radmin.com/download/index.php[/URL] (Radmin server 3.5)
 
I've tested the new Radmin server 3.5.1 installer and confirmed it resolves the problem stated in this thread.

Test procedure:
I confirmed Radmin server 3.5 was working, and then installed the KB4022716 update.
After rebooting PC to complete Windows update install I confirmed that Radmin viewer is able to connect to the server, but no image is rendered. Only the Radmin logo appears in the center of the screen. The Radmin server system tray icon is also not visible.
I then stopped the Radmin server using the Start menu shortcut, and installed the new 3.5.1 version on-top of the already installed 3.5 version. The new version installed without requiring a system reboot, and automatically started the Radmin server service again.
I confirmed the Radmin server system tray icon is visible now.
I was then able to successfully connect to, and control, the Radmin server.

I will update and test the rest of my affected Radmin servers tonight.
Edited: eikichi - 06.07.2017 12:34:14
 
I had the exact same problem. The 3.5.1 update fixed it for me, too.
 
It works.
Awesome!Very thank you!
 
does it work on IP 16232?
me has stopped again.
 
Does 3.5.1 affect the windows 7 machines? What I mean to say is, is there any point to upgrading all machines to 3.5.1? It has resolved our issues with Windows 10 update...
 
There is no need to upgrade all your servers to 3.5.1. if you don`t want to (3.5.1 will not affect any other OS).
 
Quote
Anna Kovalevawrote:
There is no need to upgrade all your servers to 3.5.1. if you don`t want to (3.5.1 will not affect any other OS).

Thank you!
 
Quote
ikanekowrote:
does it work on IP 16232?
me has stopped again.

i report this issue on May before. radmin 3.5/3.5.1 do not work after windows 10 creators preview 16193.

---

Ok, there is an
official answer: we had this issue before on insider builds, it was
always fixed on release version, so insider versions are supported "as
is" and Radmin may work incorrectly on them.



Best regards,
Famatech Support Team
 
Quote
Alex Howrote:

Quote
ikaneko wrote:
does it work on IP 16232?
me has stopped again.
i report this issue on May before. radmin 3.5/3.5.1 do not work after windows 10 creators preview 16193.

---

Ok, there is an
official answer: we had this issue before on insider builds, it was
always fixed on release version, so insider versions are supported "as
is" and Radmin may work incorrectly on them.



Best regards,
Famatech Support Team
yes. its only report on IP SlowRing environment.
Thanks for reply me!
 
In my computers version 3.5.1 solve problem.
Is version 3.5.1. without tray icon?
 
There is an 3.5.1 NTI version which you can download here here - [URL=http://support.radmin.com/index.php?/Knowledgebase/Article/View/2/9/How-to-hide-the-Radmin-tray-icon]http://support.radmin.com/index.php?/Knowledgebase/Article/View/2/9/How-to-hide-the-Radmin-tray-icon[/URL]
 
3.5.1 was working fine for me with the latest creators update patches until I installed Hyper-V. Afterwards it showed the same behavior, splash screen with full control and view only, other modes worked fine. Then I removed it and when I tried installing radmin server 3.5.1 it kept failing. It wasn't until i removed Hyper-V that I could install radmin server again. With Hyper-V removed full control and view only are not working.
 
Ugh. 2 hours going crazy because of a Microsoft update. Figures. Once again, thank you for the excellent software.
 
Hi all

I'm seeing a BSOD with v3.5.1 on Win10 1703 15063.540

The BSOD references "dxgkrnl.sys" which is a DirectX Kernel Driver

It only seems to be affecting some servers (in my case, running Intel Graphics 3000 or 4000)

I am able to trigger the BSOD by any of the following in most cases:

EITHER:
A.1) Radmin configured with "Load mirror driver on startup" enabled, or:
A.2) Client connected to Radmin server using "View Only" or "Full Control"

AND:
B.1) Trying to update the Intel drivers
B.2) Trying to restore the system from Sleep Mode
B.3) Switching monitor/display output with function keys on laptop (FN key+F5 on Toshiba laptop) for projector output

At first I thought it was the mirror driver, but as I say, even without the Mirror Driver I am still able to trigger the BSOD (with any of the above steps) on the remote host once I've tried to establish a "View Only" or "Full control" remote capture session to the host without the mirror driver installed. So this leads me to believe that the problem relates to how Radmin is capturing the display using directx?

I have tried to reinstall the graphics drivers as well as DirextX

As a temporary workaround I have disabled mirror driver from loading on startup, so that the screen capture isn't being invoked unnecessarily in the background. Now the crash can only be triggered while the server's display is being viewed by the Radmin client. Still a bug which needs to be addressed though
Edited: fragtion - 07.09.2017 07:46:53
 
Same issue after update KB4038788. Uninstalling update helps and Radmin is working.
 
It is fixed in Radmin 3.5.2.
Pages: 1
Users browsing this topic (8 guests)

Radmin 3.5

Windows 10 Compatible

DOWNLOAD

Free for 30 days

BUY NOW

Only $49 per lifetime license
for  50 PCs - $29.8 per remote PC
for 100 PCs - $24.9 per remote PC
for 150 PCs - $23.3 per remote PC
from 200 PCs - $22 per remote PC
Follow us on Twitter
Famatech Corporation Copyright © 1999-2018 Famatech. All rights reserved.