AcuToWeb Desktop conflicts with Edge on Windows 10 Enterprise

0 Likes

Problem

AcuToWeb Desktop may show some conflicts when Edge is used as browser on the client device:

1. "Connection to server refused, access denied"
It may occur when AcuAccess file has <same as client> as Local Username.
Trying to connect to an alias, the error is shown using Edge, only.
Any other browser will work correctly with the same configuration.

2. AcuToWeb Desktop remains in "Listening" mode and no new "Waiting for alias" process is started.
Using Edge, the ATWDesktop "Waiting" process never comes up, even after having hit F5 for 10 times.
Any other browser will work correctly with the same configuration.

Resolution

Both issues are caused by a restriction of the Edge browser itself.
The Localhost loopback is blocked.
The option "Allow localhost loopback (this might put your device at risk)" is ignored under 10 Enterprise. But it is working under 10 Pro.
This is a bug in the system.

To solve the situation, open the DOS prompt "As Administrator" and launch the following command-line:

CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

Restart Edge and it will work correctly.

See the following post for further info:

Localhost loopback do not work for the latest Edge 38.14393 under Windows 10 Enterprise .14393
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10082889/

SI 3125604

Comment List
Related
Recommended