Jump to content


  • Posts

  • Joined

  • Last visited

About pwhittemore

  • Rank

Profile Information

  • Location
  1. If you received a blue screen installing ESET, it means there's already another problem on your machine. Make sure your Windows Update says there are no more updates to apply, and especially check the driver for your graphics card (Intel AMD/ATI, nVidia, etc) to see you have the latest version. Another possibility: the existing problem may be that it is already infected with a virus. ESET probably has some procedures you can follow to clean an infected machine.
  2. Looks like OpenVPN 2.3.2-I002 installer had a problem. The latest VyprVPN installs OpenVPN 2.3.2-I003: "The I003 Windows installer fixes a signature problem in tap-windows driver, which prevented the driver from being installed in many cases." hxxp://openvpn.net/index.php/open-source/downloads.html Given my recent troubles, I suspect this is a major understatement.
  3. System Restore was repeatedly useless. What saved me was that I had full disk image backups from just before the ESET update. (Coincidentally taken that morning.) The problem has been identified. By carefully reapplying updates from that backup point, I have identified the problem as an issue with GoldenFrog's VyprVPN 2.x upgrade. While that upgrade is mostly a new user interface, it also updates OpenVPN to 2.3.2, and there was some kind of a problem between the two of those, in combination with a bug, but also if you attempted to start the VPN software without a system restart (which is the installer default). It was critical to uncheck the "start now" box and restart the machine first. As you can see here, the 2.0.1 update supposedly fixes a problem that can result in Skype reporting "disk I/O error" on logins. That was one of my symptoms. However, I found that upgrading to 2.02 (current release) did not resolve this problem. In fact it was almost like a virus, if you have ever run 2.0.0, even temporarily on the way to 2.0.2 (which was the case if you allowed VyprVPN to autoupdate), then you were screwed. The problem would persist even after a Windows' "System Restore" to return to a restore point taken just before the upgrade. The key... the trick... is to download the latest VyprVPN, install it but do not start it, then reboot (without starting the VPN software). Since restore points did not undo the problems, I was lucky to have a full disk image backup from that morning prior to the first upgrade of VyprVPN and OpenVPN, which happened to also be the evening that I upgraded ESET to version 7. (It seems that was update day for me as several other packages were also updated, plus Windows Updates.) So ESET is off the hook. I have updated OpenVPN and VyprVPN as described above, all was well. Then applied ESET 7 and that went well. Windows Update is continuing to run without the earlier error code. If you have trouble with ESET 7 installation, I advise you to check if you have VyprVPN installed (which is wonderful and has been as reliable as ESET for me until this) and/or OpenVPN installed (which may in fact be the trouble here). Also if you have Skype login "disk I/O" errors. I don't think the LiveUpdate or SEP installations were to blame at all; in fact they were restored by my disk image restore and I have been a bit afraid to remove them again using the ESET uninstaller now that all is working again. (The official Symantec online instructions for uninstalling SEP are about 35 fairly complex steps.) It was definitely either OpenVPN or VyprVPN itself.
  4. Also I should mention that on my latest System Restore attempt (to the ESET 6 installation prior to the upgrade), the A/V component failed to load it's configuration. I'm thinking it has been upgraded to ESET 7 and the configuration files cannot be read by ESET 6 (i.e. a one-way change). Windows Update reports that it is up to date with that Restore, so I'm going to try to uninstall ESET 6 and reinstall it to see if I can't get ESET working again. Then create a restore point and try moving forward again from there.
  5. FYI, it seems issues are not yet resolved after all. With no AV software listed by the uninstaller tool, I reinstalled ESET 7 and all seemed well. However I have since found that Windows Update is reporting error 80070005 when it gets to the installation part. Searches for that error seem to indicate issues related to anti-virus software. Also Skype cannot log in due to "disk I/O error", which again is very unusual and consistent with AV software. I've done a few System Restores now, trying to find a stable "before" environment to build on, but no luck with that. I may have to do a full fresh reinstall to continue. I think the BSoD during the ESET 7 installation left some nasty issues that aren't corrected by the uninstall or the System Restore operations. Anyway, be careful out there. Putting my story out there just in case anyone else reports issues similar to these symptoms.
  6. I've sent Peter the links to the files. Since running the uninstaller tool on all 3 of the installed AV installations, and a fresh ESET 7 installation succeeded, I consider this now resolved for me, unless there's some other way I can help investigate it further. Thanks for the fast answers, ESET folk! (I've been an ESET user for many years, after having tried many others. ESET has been the only completely reliable package for me, for years, until now, and this is looking like a Symantec problem to me.)
  7. I could but I will need a private way to send it (such as an email address or private forum message) as I don't know how much personal info is in the DMP file. The SysInspector log is incredibly thorough too but looks okay, still I'd like to post a link and send you a password privately, or at least email an unsecure link privately. Is there a way to DM/PM you on this forum? Also as a followup, the installation of ESET 7 went well, no problems at all, after I had used the uninstall to clear the existing 3 items. It completed without incident and I'm running a full scan now. EDIT: Spotted the DM feature. Will DM you a download link for use by any staff.
  8. I have the SysInspector log zip and the dmp file from after the System Restore after the BSoD, before uninstalling anything more. So it's ESET 6 at this point. I'm going through the process now to uninstall, clean up. The uninstaller reports: 1. ESS/EAV/ESMX 2. SEP 3. Symantex LiveUpdate I'm not sure what SEP is (Windows Firewall?) and definitely not sure why LiveUpdate is there. It does not show in installed software, nor do I have ANY Symantec stuff installed. This is a fairly recent Windows 8.0 fresh install (new SSD) and then 8.1 upgrade so I'm really confused about how LiveUpdate got on there. (If it's really LiveUpdate.) Okay, I just looked up SEP too. SYMANTEC Endpoint Protection? Really? Okay going to uninstall them all. Restart, then try the ESET7 installation. Wish me luck, I'm going in...
  9. I'm having the same issue. Immediate BSoD during the ESET 7 Installer run. Windows 8.1. My machine was unbootable after that. I had to do a System Restore which rolled back many software packages. I've been catching up again. Sent a message to ESET Support and received a response suggesting I fully uninstall and reinstall rather than upgrade. Why does ESET have such a good update process, and nice pretty Update buttons if we aren't supposed to use them? In case I'm misunderstanding, here is the meaty part of the Support response: "We apologize for the errors that the upgrade has caused you. In the future, we recommend uninstalling any previous version of ESET first, then installing the latest one from our website. If this resolves your issue or if you need further assistance, please let us know by replying to this email." I replied.
  • Create New...