Windows 10 Remote Assistance (msra.exe) will need 45 seconds to connect from Win10 1809 or 1803

  • Thread starter Thread starter Ronald Schilf
  • Start date Start date
R

Ronald Schilf

Guest
After upgrading the IT department to Win10 v1803/1809, we noticed that Remote Assistance (MSRA.exe) has a problem.

Please note: this problem only surfaces on systems that have no internet access!

Steps to reproduce:

1 Take two systems (Win10 180x) that are on the same network but have no internet access (either remove the gateway IP or simply take 2 VMs connected to default virtual switch [which is connected to: internal network by default])

2 on one system, create an invitation file on the command line like this:

msra.exe /saveasfile %userprofile%\desktop\help.msrcincident 111111

3 take that file and transport it from your desktop to the other machine (use a share, USB stick, RD-clipboard,...) and open it on the other machine

Expected behavior, as seen on on any win10 version prior to 1803: you will be asked for the password, which we set to 111111 and you enter it and immediately, you connect

Observed behavior, as seen on win10 v1803 and 1809: after clicking on the invitation and entering the code, there is a delay of exactly 45 seconds with the status "attempting to connect". Afterwards, everything works.

Since this is seen on any system, Microsoft will be able to reproduce this in seconds.

It happens no matter what target operating system the person you want to help is using, as long as the person who would like to offer help is using Win10 v1803 or v1809.

---------------

Please refrain from telling me that there is a newer app "Quick Assist", since we need an app that works offline and QA does not. This is a big nuisance for our support team and we need to get rid of this delay.

More...
 
Back
Top