laopa

Member
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

0 Neutral

About laopa

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    Stuck between the Indian and Pacific Oceans
  1. OK running 11.0.05958 Beta and all seems OK. No BSOD for a few days now and all Chrome based Browsers running OK in Sandboxie. Plus, drum roll for excitement, I now an getting full functionality from HostsServer and HostsMan. This may well be like an early Christmas unless "the Wosarnator" has any bad news or comments? Otherwise ring the bells and prepare the slays! We are off! Then again? We kill the whole Beta Update thing ....... when?
  2. OK thanks, I am now running EIS Version 11.0.0.5935 Beta. So far for the last 48 hours I have had no BSOD Crashes. Based upon prior experience I am not convinced yet but this looks very good to date. Give it another two days and you got me. Thanks for all the Support. PS Chrome Based Browsers in Sandboxie seem OK. PPS I am getting no Log Recordings in HostsServer which I use in combination with HostsMan? No doubt considered redundant by some!
  3. Hi Andrew, Well everything was great until it BSOD Crashed again. Yet another Dump File attached. Thanks for all your efforts to fix this Hi Fabian, "Depending on the feedback we get from you and other affected users it shouldn't take too long." As you can see the BSODs continue however Chrome based Browsers in Sandboxie are still working OK. Sorry about that. Here's hoping guys. 111815-39031-01.zip
  4. @Peter2150 Hi, Now that is a snippet of information that would have been good to know. Enabled Beta, downloaded, installed, rebooted and left Enabled. Google Chrome is in Sandboxie and working and as for the BSOD I will have to wait and see. Does this mean that I (we all) are a Beta Diet for life? Can we switch back when and if we get a fully functional stable version? How will we know when it is available? Thanks
  5. Hi Fabian, Just the response I would expect. I'll wait and see.
  6. @Andrew F Hi, Thanks for getting back and the your efforts in fixing this. So I turned on accept beta updates and updated and then rebooted my system. The good news was that the beta seemed to have fixed at least the Chrome + Sandboxie issue. I can not tell about the BSOD. So I turned off accept beta updates. The bad news is that about an hour later another update, seemingly not a beta, occurred requiring a system shut down and now Chrome (Vivaldi etc) in Sandboxie are broken again! One step forward and one step back. The joys of product development. Can't wait for the next BSOD. Tick, tick ..... a few hours later. The rest of the bad news, my latest BSOD. Opera (12.7) in Sandboxie streaming content. Boom. Getting sick of this but with high hopes. Keep trying guys, we are all with you. So I guess that would be a yes/don't know for the beta and a no/no for the later "update". I await. 111715-24648-01.zip
  7. Great to get the Emsi Feedback on the Dump Files I have Posted! NOT! Power to you CP! Anyhoo here is yet another BSOD related to EIS 11. Thanks Fabian! (from Wilder Forums) Can I submit "the costs" of the damages that this is doing to my PC and Laptop and Consulting Business to Emsisoft? Yeah, Yeah, I know you are working on it .... yet again. 111615-32183-01.zip
  8. Well, Here we are again with BSOD number 6 or 7 since Friday 13th and the unilateral upgrade from stable EIS 10 to clealy unstable EIS 11. Opera (12.7) in Sandboxie Streaming Content. Recently upgraded latest version Chrome x 32 to Chrome x 64. That did not solve the Sandboxie issue. However Chrome x 32 and now Chrome x 64 did/do work outside Sandboxie. Attached is yet another Mini Dump File. fwndislwf64.sys (Emsisoft Firewall Engine, Emsisoft Ltd) WhoCrashed reports the above as the likely culprit. I think that has been the supposed issue in all of the MiniDumps I have attached as requested. Yeah, I have been told here previously that WhoCrashed is of no use, but for us lesser than other self confessed coding geniuses, it will suffice to point us at least in a likely direction. I am still not in a happy place with this! 111515-31496-01.zip
  9. Hi, Well I hope the Zipped Mini Dumps of the BSODs are attached. There are three attachments as my PC has just BSOD Crashed twice more since I first Posted. Today 14/11/2015 = Opera Browser (12.17) not in Sandboxie and Streaming Content. Later Opera Browser (12.17) in SandBoxie 5.06 Streaming Content. Switched back to ESI Firewall On and my Belkin Automatic Power Management Software is back. Still BSOD Crashes. Seriously if Emsisoft knew there were stability issues related to Chrome, Sandboxie etc. why did they unilaterally upgrade us all to ESI 11? Looking forward to fixing this and getting some answers. Thanks Minidump.zip 111415-30903-01.zip 111415-24788-01.zip
  10. Hi, This feels like deja vu on the last major ES Update around Jan 2015. That was supposedly an IPv6 issue? My Win 7 Home Premium 64Bit PC has crashed four time so far today after the auto update to ES 11.0.0.5911. If relevant I have been streaming content before all crashes. WhoCrashed reports that it is the ESI Firewall that is causing the BSODs. I have disabled the ESI Firewall and am running the Windows Firewall. (that idea did not work as the PC has BSOD Crashed after disabling EMSI Firewall) Chrome will work but not in SandBoxie. Nor will Vivaldi. Sandboxie as reported in other Posts does not work properly with the ESI Update. The Update also seems to have killed my Belkin Automatic Power Management Software. There may be other affected programs that I have not discovered yet. A "Leap in Technology" it might be but it is a "Gigantic Step backwards in Stability". Again like last time EMSI throws its users and customers to the wolves with clearly unstable Security Software. How is this possible? I better get this posted before my next BSOD. Help!
  11. Hi, Given where you are always coming from, you might enjoy these. laopa
  12. Hi, Just to clarify the IPv6 figures. OK let's live with the Google Stats. firstly the 01/01/2015 figure for the World Average = 5.84% more germane to our discussion is that the USA = 14.59% Germany = 14.59% Norway = 9.15% France = 6% Suffice to say that in the markets where, I would assume, Emsisoft makes a large proportion of its sales and where a large proportion of its users/customers are, then the uptake of Ipv6 is 2 to 3 times the World Average you misquote. Even if it was only 5% as you incorrectly stated, then if we assume that EIS users/customers actually connect to the internet then you could also assume that 5% of them are going to be using IPv6? Not 0.01% and not 0.2% but 5% and as stated above, this would in reality be 2 - 3 times that many users/customers in Emsisoft's Major Markets using EIS, having IPv6 and suffering from unexplained and clearly related BSOD? I know you do not see that many emails and visitors to this forum but those are the potential realities of how many EIS users/customers (5 - 15%) could be having BSOD crashes without having any idea of what is causing them!. Minimize that. laopa
  13. Fascinating how you like to remove negative posts by your users/customers but keep the derogative/denigrating comments of your staff.
  14. OK now we have a real issue, You publish on the web details of my email address and ISP in an attempt to justify your incompetence and annoyance. Not Acceptable EMSISOFT. You need to FIRE this dude and move one. laopa
  15. All hands to the Battlements - Barbarians at the Gate - Barbarians = Users/Customers with questions! Didn't get this on PC or Laptop - my bad - my fault of course! I love your ability to invent numbers/statistics to suit your arguments and apply them in such a sarcastic tone, That is TOTAL Analytical Rubbish! It takes NO consideration of the number of users/customers who have NO IDEA that their BSOD are related to Emsisoft EIS. So if they don't know it is your fault makes it OK???? Even in your limited and somewhat bent view you managed to up the "incidence" from 0.01% to 0.2% - that's like a 20 times increase. Cool! That was not my point and you know it! Nothing at my end but let me guess --- that would also be my fault, again! I'll let "stapp" know that I should not bother to follow his/her advice to look at WinDbg. Save your efforts, we all know there are holes in the bucket - just fix them and stop telling us about the benefits of doing nothing! laopa