Reset SPAD.neXt license

Delete the file "%APPDATA%\SPAD.neXt\SPAD.neXt.lic

How to properly open a Support Ticket

  1. Start SPAD.neXt

  2. (reproduce problem)

  3. in SPAD.neXt click in Settings->Support

  4. and either Select an exiting ticket from the list and click on UPDATE TICKET or click on Create new ticket

  5. Add any info needed and hit submit.

Note: if for reproducing the problem no simulation connection is needed please do so from a fresh SPAD.neXt start without Simulator running. If simulator is needed do it after a new start not after a over the pond flight It's no joy to gravel through megabytes of unnecessary logfiles if you update the ticket after a 5 hour flight. Processing of such tickets is declined.

Available SPAD.neXt update channels

There are 3 update channels available for SPAD.neXt

  • Release: This is the public release of SPAD.neXt. Your SPAD.neXt installation will automatically update to it, if your update subscription is valid for it

  • Beta: The upcoming pre-release, available only for "Complete Edition"-License users , or when assigned for special tests

  • Alpha: The current development version of SPAD.neXt. This update channel is invite only for early adopters. To apply for participation, open a ticket from within SPAD.neXt. Development focus of current Alpha version can be reviewed in the SPAD.neXt-Discord in the apropiate #release-faq thread

To change your update channel, head to Settings->Application->Expert in SPAD.neXt. All update channels available to you will be selectable.

Windows Defender claiming "Trojan:Script/Wacatac.B!ml" Infection

All releases of SPAD.neXt are virus scanned against the 3 most common scan-engines, and all executables are digitally signed. However sometimes Windows Defender will complain when trying to run e.g. a Plugin-Installer and claim it being infected with "Trojan:Script/Wacatac.B!ml". This is a known Problem of how Windows Defender handles compressed files sometimes and usually is a false-positive. First countercheck that the digital signature of the file is intact:

  • Right click the file and select "Properties"

  • Select the tab "digital signature" and confirm it states "signature is valid"

If the signature is intact, you need to update you Windows Defender virus database and clear the detectioncache:

  1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender

  2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”

  3. Run "MpCmdRun.exe -SignatureUpdate"

If the signature is not intact. Delete the file immediately and report to If in doubt, you can always submit the file to Microsoft for analysis.

Last updated