Has anyone resolved the issue of not being able to exclude the flightsimulator.exe and other associated MSFS files from Anti-Virus software (Firewall) warnings?

I purchased MSFS via the Microsoft Store.

 

I did exclude MSFS, no problem. Using Kaspersky Internet Security

1 hour ago, willy647 said:

I did exclude MSFS, no problem. Using Kaspersky Internet Security

And you purchased MSFS via Microsoft Store directly?

The folder and exe are protected by Windows and it's excruciating attempting to unlock it to allow Bitdefender to access it and exclude it.

AFAIK I'm not the only one experiencing this issue-hence I posted here 1 month after release to see if anyone has come up with a no-nonsense no BS way to resolve it.

MSFS is the only program I cannot access for anti-virus.

So if you've found a way, I'm all ears and eyes.

I have no problem using MS Store MSFS2020 and Win10 Defender. 

 

But you have to get full ownership over the MSFS folder, where the exe is! 

Is not required to gain ownership of the MSFS folder, if the goal is only adding the .exe to the A/V Exclusion.

In MS Windows Defender, it's enough to create an Exclusion "by process", and type only the name of the executable, that is FlightSimulator.exe, which will add it to the exclusion list regardless of its location, since the exclusion by process is only connected to the process name, as presented in the Task Manager.

Edited September 18, 20205 yr by virtuali

Thank you virtuali.

3 hours ago, virtuali said:

Is not required to gain ownership of the MSFS folder, if the goal is only adding the .exe to the A/V Exclusion.

In MS Windows Defender, it's enough to create an Exclusion "by process", and type only the name of the executable, that is FlightSimulator.exe, which will add it to the exclusion list regardless of its location, since the exclusion by process is only connected to the process name, as presented in the Task Manager.

correct, you don't need to totally exclude it, from what I understand they "forgot" to digitally sign the exe. The security software is simply doing it's job. It doesn't know who it's from or what it is and because it acts like malware for it's DRM it make security software act the way it does, you just need to add it to the Trusded list and hope they sign it for future updates.

13 hours ago, virtuali said:

Is not required to gain ownership of the MSFS folder, if the goal is only adding the .exe to the A/V Exclusion.

In MS Windows Defender, it's enough to create an Exclusion "by process", and type only the name of the executable, that is FlightSimulator.exe, which will add it to the exclusion list regardless of its location, since the exclusion by process is only connected to the process name, as presented in the Task Manager.

 

9 hours ago, FPStewy said:

correct, you don't need to totally exclude it, from what I understand they "forgot" to digitally sign the exe. The security software is simply doing it's job. It doesn't know who it's from or what it is and because it acts like malware for it's DRM it make security software act the way it does, you just need to add it to the Trusded list and hope they sign it for future updates.

Thanks gents, I appreciate your input.

However, Windows Security is advising that my AV (ie Bitdefender) is in control of all aspects and all areas in Windows Defender are greyed out and not allowing me to add exclusions via the usual way - ie: Firewall & Network Protection and Virus & Threat Protection are greyed out.

Despite this, I attempted to go to Windows Firewall (Inbound & Outbound Rules) and type "flightsimulator.exe" (without quotes of course) and this had no positive effect. 

As soon as I opened MSFS, Bitdefender displayed the usual "Allow or Block" messages (and there are 6 popup messages that appear in total each time you click Allow) before they clear.

Another thing to note for the tech savvy persons here - that despite attempting to attach the flightsimulator.exe file located Users->WindowsApps->MicrosoftFlightSimulator_8WEK (etc etc), the message popup from Bitdefender shows a different location.

It isn't displaying the entire path (not enough display area in the popup box) but from what I can see this is not the same directory path? Is this a clue?

 

if you have the "free" version it's complicated, it's kinda locked for adding exclusions and such, but they are also weird when it comes to exclusions itself. Also Bit takes over to a point from Defender but how much I don't know.

But again the best thing is not to exclude coz it has to do drm stuff that is "unknown to us mortals" it's just best to add it as a trusted application so that it's allowed to do it's thing, how bit does that I'm not exactly sure.

I use esetAV and I just browsed to the flightsimulator.exe file and excluded it. It will have no effect on DRM because it doesn't hide the file, it just tells the av not to scan it.

 

Vic

13 hours ago, FPStewy said:

"forgot" to digitally sign the exe

And this is a MS product?  Don't get any better..or worse!

I''l bump this thread.  I've just installed MSFS from the Store and have to turn off AVAST in order to start the program.  AVAST shows the offending .exe buried away in \GLOBAL ROOT\Device\Harddisk Volume20\Flightsimulator.exe.

I've tried to add exceptions the usual way - both AVAST and Defender appear incapable of registering this.  I'm also amazed that AVAST has not cleared this .exe as a 'clean' as there must be tens of thousands of AVAST clients MSFS.

As an aside, since installing MSFS, my Windows 10 fails to boot first time and has to be brought into life via the reset button.

Anti-virus programs do more harm than good. Especially 3rd party ones. If you must use one, the default Windows Defender is the better solution.

I have used Webroot for years, never had a problem with it interfering with any program. 

On 9/18/2020 at 10:56 PM, Adrian123 said:

And this is a MS product?  Don't get any better..or worse!

They do not digitally sign the SDK installer either. Every time they release a new version, Windows Defender tries to quarantine it as potential malware when I download it.