Failed to connect to the simulator - Out of ideas

So I suddenly seem to be unable to connect to the simulator for some reason...

It does work in safe mode, using a port monitor tool I noticed that in safe mode 2 instances of simulator are started vs 1 in normal mode.

One listeining on port 1234 and one on port 42877, in normal mode only the 42877 instance is running...

What have I done and tried so far:

* Uninstall my antivirus completely

* Disable windows firewall protection

* Different SDK version

* Reinstall eclipse, connectiq and sdks completely

* Remove .m2 and .eclipse folders in the process

* Manually allowed all connections from/to simulator.exe in firewall

* Check if ports are in use by something else (nope)

* Start simulator.exe manually (both as normal user and as admin)

I am running out of ideas, apart from wiping windows and clean install everything... but that's not worth it, in that case connect iq development will be limited to another place

This is on Windows10 x64. latest update, no spaces in path/names of connect iq sdk or projects...

If anyone has any idea! (Perhaps figure out if simulator.exe on 1234 is somehow blocked? Can't find any signs towards that)

0 xberzerker 5 days ago

the safe mode worked! which means some windows resource is in fact blocking the port request. i've fully removed hyper-v and netsh int ipv4 show excludedportrange protocol=tcp showed no 1234 ranges. later today i will remove wsl, hope it is the one to blame.

0 Ultra 5 days ago in reply to xberzerker

It may of course just be that you don’t hsve the correct firewall rules set for it. I have both hyperv and wsl running when I use the simulator without issue.

0 xberzerker 5 days ago

i've learned so far that under healthy conditions, if no rule is set, firewall pops a prompt asking for allowance under private or public networks. that was what happened the previous times i got this (temporally) fixed.

i've tried to cleanup and reinput rules manually too. tried even disabling firewall.

today i was set to REMOVE WSL, AND for my surprise i found HYPER-V enabled, so i removed both.
AND THE PROBLEM WAS SOLVED!

so, i know there is a way to make everything work in harmony somewhere, but now i've spent way too much time with this already. anyway, we're building up some knowledge here, right? next time this break -coz it will- i promise to research further till we find the real culprit.