I had same trouble with FP but setting an exclusion to the vbs files fixed it with windows Defender
fwiw other antivirus packages are going after them as well
and yet none of them come outright and say the VBS itself is bad
I also excluded the game process as it seems to be a combination, perhaps with how the game is executing the vbs files
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\Windows\system32> Add-MpPreference -ExclusionPath "c:\pinball\FP\Scripts\*.vbs" PS C:\Windows\system32> Add-MpPreference -ExclusionPath "c:\pinball\VPX\Scripts\*.vbs" PS C:\Windows\system32> Add-MpPreference -ExclusionProcess "c:\pinball\VPX\VPinballX.exe" PS C:\Windows\system32> Add-MpPreference -ExclusionProcess "c:\pinball\FP\Future Pinball.exe"
In admin powershell window (you could copy and paste the above and just adjust for your paths/names
If you have several betas, you could wild card the process to "c:\VPX\VPinball*.exe" etc
VpinMAME doesnt use scripts so i have had no issue with it.
For FP, BAM needs no exception as it is not the guy loading the VBS




Top










are all trademarks of VPFORUMS.