-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows access permissions preventing ui start-up #33
Comments
firewall or antivirus settings of some sort? windows is weird. |
i can say that it works fine on vanilla windows 10 with windows defender. you may have some other software that prevents it from opening a listening socket. |
I've got stock Windows Defender and Windows Firewall. Windows version is 1809. There's nothing on port 1992 at all and I couldn't see if there was a way to pass an alternative port through from the command line - thinking about it now I had an issue with Loopback trying to bind to port 3000 which I hadn't seen before, and I thought that might be a way of tracking down the cause of this. |
The port 1992 is being reserved by Hyper-V which is also used by docker desktop. See: googlevr/gvr-unity-sdk#1002 |
After a while not doing anything with Mongoose OS, an upcoming project saw a need to evaluate its suitability. However, something has changed in Windows in the 11 months that have passed - it might be the standard MS updates, or upgrading to Win10 Pro to run Docker, I'm not certain.
When I try and launch
mos.exe
for the UI, regardless of whether I'm in a standard or administrator shell, I'm getting this error:mos.exe version
reports that I'm using v2.10.2, but I had the same error when I tried to run the older version I had, from February 2018.Is there anything I can do to get around this?
The text was updated successfully, but these errors were encountered: