Hi,
Just downlaoded the latest "Lite" version of Tickstory and got a Windows Defender critical warning of it containing a trojan "Win32/Spursint.A". Thought you ought to know!
I have not bothered to update to the latest version of code!
David.
Trojan in latest download?
Re: Trojan in latest download?
Hi David,
Thanks for notifying us of this. Couple of questions so we can follow this up:
- Which version are you referring to - the free Tickstory v1.5.3?
- When does the notification occur? During download? Installation?
- What version are you upgrading from?
- What version of Windows are you using?
My guess is that if Microsoft have recently updated their Windows Defender tool, you'll probably get the same message if you try to reinstall the same version you're using. We'll report this information to Microsoft so they can hopefully resolve it as soon as possible.
Thanks.
Thanks for notifying us of this. Couple of questions so we can follow this up:
- Which version are you referring to - the free Tickstory v1.5.3?
- When does the notification occur? During download? Installation?
- What version are you upgrading from?
- What version of Windows are you using?
My guess is that if Microsoft have recently updated their Windows Defender tool, you'll probably get the same message if you try to reinstall the same version you're using. We'll report this information to Microsoft so they can hopefully resolve it as soon as possible.
Thanks.
Re: Trojan in latest download?
Hi David,
Microsoft has contacted us about this issue and have advised that it should now be resolved. All you should need to do is update to the latest definitions.
Appreciate if you can let us know if this has resolved the problem issue for you, otherwise we will follow up again (we were unable to reproduce the issue on our side).
Thanks.
Microsoft has contacted us about this issue and have advised that it should now be resolved. All you should need to do is update to the latest definitions.
Appreciate if you can let us know if this has resolved the problem issue for you, otherwise we will follow up again (we were unable to reproduce the issue on our side).
Thanks.