Virus or something wrong?

hello,

today I lauch the game and I receive an alert request from my firewall (native)
C:6\flightsimulator.exe (unknown publisher)

as this path is a bit curious, I blocked this request, I launched a virus scan (nothing detected) and I try to find some help here.

thank you in advance.

1 Like

Hi @CleEnk,
Do you mean an alert from the native Windows anti-virus - Windows Defender? If so, check Windows update to see if there’s any update to it’s definitions as not too long ago, it was detecting MSFS; but this has been fixed.

Is your MSFS installed on the C: drive in a folder named “6” ?

hi,

thank you for your reply.

I receive an alert from my native firewall (microsoft w10) whos ask me to allow or block TCP/UDP traffic from this executable with his curious path. I’m suspicious about this file because MSFS is located in another drive (D:). C:6\ or C:\6 does not exist or can not be reach.

anyway the game works and windows defender haven’t detect anything.

It could be how XBOX creates Xvd folders - drives (but generally they are not from the root). You can see in Device Manager how many Xvd “drives” there are. When MSFS is running, there will be more of those “disks” then go away after exit.

The flightsimulator.exe is actually located on the C: drive (if you installed from MS Store or Game Pass) - even if you chose to install on the D: drive. The only way it will go to the D: drive is if you “moved” the app there via the “Move” command or you have changed “Storage” settings for apps to go to the D: drive.

MSFS does require the firewall to open ports. When MSFS is running, those ports open. When exiting, they close. It is primarily used for Multiplayer. Once you allow it, it does not prompt again. If it keeps prompting, it may be that you have your network connection setup as “Public”.

The C:\6 is also xbox related.

I also have the same problem. MSFS is installed on C: drive but I have 3d party addons on the D drive linked to MSFS community folder through MSFS Addon Linker. Maybe that’s why I get the Windows Firewall alert on the D drive but I’m not 100% sure.

I just noticed the “unknown publisher” when flightsimulator.exe was asking for firewall permissions, and it raised my suspicions as well.

Is MS/Asobo seriously neglecting to sign their packages, or do I have malicious software masquerading as Flight Sim? If the answer is the former, then come on guys - you’re seriously undermining Windows Defender’s efforts to maintain a secure OS.

same here. got very suspicious. what is going on?

I have the exact same problem. It has happened many times.Screenshot 2021-04-19 115642

I have this message popping up only after a new sim update. So no problem for me.

why are you only allowing it to connect on Public networks? Shouldn’t you be using your own connection?

Not sure, but I think that’s the way it comes up. I always have to change it to private.

I get this firewall message very often and the installation path is in that screenshot is not the one in which FS2020 is installed.

I am still getting the same message. Every time I run the sim.

I contacted support about this. They told me to add an exception in Windows Firewall to allow the Flight Simulator executable, but they completely disregarded my concerns about it being from an UNKNOWN PUBLISHER.
Does anyone at Microsoft actually care about information security?

I am concerned about it too.
The thing is I am getting the same alert every single time I run the sim and the installation path is coming from changes too when I run FS2020.

it is normal for windows store version, because flightsimulator.exe launches from virtual address, or whatever it is, that’s why in event viewer after crash to desktop you see v0.0.0.0 as version, and there you can see this casual path, from the exe was started, by this cause i couldn’t use malwarebyte’s windows firewall control by normal way, and was forced to change rules to low(all out allowed)

Another reason to buy the Steam version.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.