Jump to content

WheelieUK

Member
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About WheelieUK

  • Rank
    New Member
  • Birthday February 13

Profile Information

  • Gender
    Male
  • Location
    London, UK, GB
  • Interests
    All things techy. (Specifically security related)
    Coding.
    php
    python
    cryptography
    travel.
    law
    psychology
    assistive technology
  1. Hi Andrew, Please see PM. Updates done and now functioning, but not without some problems. Not sure they were related to this issue, so advising more for information in case the same happens to anyone else. Details in the PM. Thanks for your assistance. Mike
  2. Responded. Will await notification for beta updates. Thanks again for all your help. I thought the forum would be slower than email responses but I am, pleasantly, surprised, at how quickly this issue was dealt with. You guys are definitely the A team where customer service is concerned. Both on-line and off.
  3. Hi Andrew, I have replied to pm via the same route. To confirm, the test solution suggested seems to be working ok. Will await further instruction on next step. Mike aka Wheelie
  4. Just to clarify, bernx has resolved their problem. Mine continues and EIS is still crashing as per my initial post in this thread. (It was hijacked by another user with a similar problem, but on Windows 10).
  5. bernx, Did you try using Chameleon from VyprVPN? That protocol would most likely work and would give you a high degree of security. I tried them before ExpressVPN. Good service, but I need access to more regions than they covered. Andrey Fedorinin I noted that there were a fair number of policy restrictions in the FRST logs I submitted. I have since corrected that error and attach a new log here. Emsisoft is still generating the same BSOD error, despite correcting the policy restrictions, so that was not the cause. This ONLY happens when trying to use the UDP or TCP OpenVPN protocol.
  6. Hi Guys, I need a little help with this one. Since the update of 23rd November, I keep getting the BSOD when I run ExpressVPN (Version 4.1.1.380) on a Windows 7 32 bit O/S. This only occurred following that update. ExpressVPN DOES NOT crash when using the LT2P or the SSTP protocol options, just openvpn. I tried uninstalling and reinstalling the following Microsoft Net Framework 3.5.1 Microsoft Net Framework 4.5.2 Emsisoft Internet Security 11.0.0.5958 ExpressVPN Version 4.1.1.380 Whilst ExpressVPN app was uninstalled, and after reinstalling the other programmes above minus Express
  7. Hi John, It may be that you will be asked to do a seperate thread for your issue. My issue is now resolved. I installed the hotfix, mentioned by Christian, and also found left over registry entries from Eset (Which I discovered as a result of using UnHackMe). Whilst the hotfix sorted out the firewall issue, it was Eset that was causing the issue with the protection. There was a driver in the unplug and play section in the device manager that needed to be deleted (I found a tutorial on Eset web site) To access the driver you needed to view hidden drivers. In addition, I also found, despite
  8. Hi Christian, I realised I should have included the dump in the previous post and attempted to do so, but your reply arrived 1st. 2 mini dumps now included. Edit Only loaded 1 the 1st time so trying again 082215-25693-01.dmp 082215-25693-01.dmp
  9. Hi All, I recently tried to update to windows 10 from a Windows 7 Sp1 32 bit machine. The update failed and put me into a continual reboot. I managed to recover the system, using system restore, to prior to the update, but then the shield goes either orange or red. Orange, when the firewall runs, which was fixed with an update (But see below) and then red when it the other protection and firewall failed to start. I get a pop up that says something like Edit "Emsisoft Internet Security (stable ( 10.0.0.5641) and beta) is unable to protect your computer. Emsisosft Internet Security wa
×
×
  • Create New...