Re: Nod32 For Windows 7
Tommye Hope
Disabling ESET's real-time protection automatically re-enables Windows Defender on Windows 10 and vice-versa. It is not possible to have two or more real-time protection modules running at a time; it would cause a big performance hit and possibly other issues as well.
Eset at installation time will disable WD realtime protection and register itself within Windows Security Center as the active AV solution. The only solution I see to this is to completely disable NOD32 while at work at which time WD should be reestablished as the active AV solution. When you leave the work network, you would then reenable NOD32.
So I've been using for several months my computer in the organization domain, but yesterday they called me from the TI Antivirus department asking me why I was not using antivirus, I explained that I was using nod32 but they said that the cannot control this so they ask me for enable windows defender so they can manage or they will block my access.
As ESET 9 was probably the only AV that could allow me to use the OS that I preferred, I gladly renewed without "shopping" for alternatives. Now ... nothing to stop me from looking for another vendor. Too bad after 15 years using this product.
By the way, I'm on my XP box using RDP to access a Win7 "drone" to use Firefox. I have needed this for some time to access some websites, such as my bank, that cut off XP with claims of "safety Issues." Seriously, they wouldn't know a safety issue if one smacked them in the head. I have not had a single issue with XP that ESET NOD32 has not dealt with cleanly in 15 years. In the last 10, I can't recall seeing a detection that wasn't me playing with something that MS doesn't like, so the AV community tries to kill it.
So please don't tell me my XP is not "safe." It is as safe as the user makes it. I know, I know ... the vast majority of users do not have my knowledge and experience and need corporations to look out for them. But when self-serving behemoths like MS do that, they sure seem to be looking to enhance their own revenue. I would have paid for a more compact and efficient version of XP with a consistent user interface that isn't trying to look like Apple.
An AV might be able to potentially help but I've always felt it's a prison with a hole in the fence. You can have security that is good but nothing changes the fact there's a gapping hole in the fence.
Hello,
Microsoft ended support for Windows XP eight years ago in 2014 and Microsoft Windows 7 two years ago in 2020. Historically, ESET has historically provided support for operating systems for some time after their developer has ceased to support them, but keep in mind this has been to allow customers time to finalize replacement with a supported operating system.
It was also very abrupt - perhaps was noted somewhere or at some stage, but I had to come here to find out what I hoped wasn't true. There's only a couple of months left on my licences so I won't worry about refunds (irrespective of T&Cs, in my country it's not legal for a vendor to bill (or have billed) for a product or service which doesn't function / is not fit for purpose advertised).
Hello,
You may wish to take a look at the Windows XP whitepaper I linked to above. Many of the recommendations there are also applicable to Microsoft Windows Vista and Windows 7. They can even be applied to current versions of Windows like Windows 10 and Windows 11, for that matter.
I do not know the exact dates and details, but there has been an extensive notification campaign going on for several years now, with in-product messaging as well as emails to customers and their distributors. It is entirely possible these were not seen for whatever reason (notifications closed and dismissed, emails marked as spam, etc.), but ESET notifications did go out.
If you are due a refund for your license based on your country's consumer protection laws you are certainly entitled to request it. Contact the local ESET office or distributor in your country and explain the situation to them.
Regards,
Aryeh Goretsky
Back in 2018, I wrote a paper and accompanying blog post, The Last Windows XP Security White Paper, which contained something along the lines of 48 pages of information on how to reduce risk if you had systems still running Windows XP.
You may wish to take a look at the Windows XP whitepaper I linked to above. Many of the recommendations there are also applicable to Microsoft Windows Vista and Windows 7. They can even be applied to current versions of Windows like Windows 10 and Windows 11, for that matter.
Thanks, read the whitepaper. Most of those things I have already done, or know. But it lacks some reality for my situation and experience - there is another side to its arguments. Eg an SSD with good GC does not slow down "even to speeds slower than those of hard disk drives" due to lack of TRIM, but a file with 10k fragments does in practice so still needs some defragmentation. The paper pushes need for NAT firewalls, but these are near-ubiquitous in 'power user' situations, so being connected to the internet to upgrade is a non-event. "Vulnerable to attack" can be interpreted different ways - while technically true (and the Right Thing for a security company to say), in objective reality (statistically) is a bit misleading as to what actually will, or can happen. The reality is all machines are at nonzero risk (which many people consider "significant"), as the continual stream of urgent patches to modern OSs proves. Windows' (all versions afaik) behaviour itself limits security, eg disallowing multiple usernames for network shares limits fine-grained access, leading to ad-hoc networks using unsecured shares or wide access (exposing 1TB of business data via a single share). That (the ransomware hole), dodgy software (viruses, trojans, bad web scripts) and outright social manipulation, is how things get in, as I see it - the fact is there are many things worse for security than a decision to run an old OS somewhere.
And that is where (and why) a good antivirus is good at mopping up the many extant risks that remain irrespective of OS version or any single setup issue - even if it never actually triggers on anything.
I do not know the exact dates and details, but there has been an extensive notification campaign going on for several years now, with in-product messaging as well as emails to customers and their distributors. It is entirely possible these were not seen for whatever reason (notifications closed and dismissed, emails marked as spam, etc.), but ESET notifications did go out.
I looked into this: I had desktop notifications turned off, from memory because it was popping up orange about end of life every other day (without actually doing anything for months or perhaps years). In this circumstance I think turning them off was the only thing to do (given that the product was bought for XP and Vista). I left alert windows and in-product messaging turned on. Also I'm as certain as I can be there were zero email communications. I was unaware of any specific dates, and would have been very alert to anything specific, which is why it came as a surprise.
d3342ee215