Jump to content

daveiw

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by daveiw

  1. Just to clarify, with SSL filtering on and https checking enabled in 'web protocols' I can browse most sites okay, much of the time, however if I try to search through my address bar - my preferred method, the first time it works, all subsequent searches fail with a bad connection error.

  2. I have not come across such issue. What version of Chrome do you use?

    Also, does the issue persist when you close all browsers, disable SSL scanning, open a browser, close it again, enable SSL scanning, open the browser again and browse some websites?

     

     The latest version of Chrome and yes it does, I also note that there are 2 entries for Chrome under the List of SSL/TLS filtered applications, is that normal?

  3. Hello, as we all know SSL filtering is enabled by default in Eset Beta 9, however I'm having issues with it. 

     

    I can't perform more than one search from my Chrome browser bar without a failed to connect message popping up, the only way to enable normal browsing is to either switch off the option completely in enable ssl/tls protocol filtering, or switch off enable https checking.

     

    The reason I'm posting this is more to find out if others are having the same issue, or whether it's just me? Asking as I can only find old references to similar issues for Eset prior to version 9.

     

    Thanks in advance!

  4.  

    In my case windows10 and Eset SS 8.319.1
     
    This value not work
    %SystemRoot%\SysWow64\windows.storage.dll (Why @Marcos you tell to all to change to this value?) 
     
    I change value from
    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
    and
    HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
     
    to %SystemRoot%\system32\windows.storage.dll
     
    And yet all is ok
     
     
    And dear @Marcos the first human that understand issue is related to Eset And explain how reproduce it is JAMESWT and first human that Found the solution with regkey it is AREZCO.
     
    And the issue in General was discovery by users from Eset forum and tenforums and i Thanks all People that contribute to the thread. 
     
    All users from forums was able to reproduce the issue at first trytime..  Only eset not....  But Thanks to do a update that sometimes solve the issue and Thanks to update eset SS 8 and 9 to solve the issue 

     

     

     

    I think the important thing is that Eset as a group managed to sort the issue out, I do however question the apologists, that blamed everything other than the generally brilliant Eset software - however I can see from that reasoning why they would.

  5.  

    Issue fixed. According to procedure mentioned here. I manually changed those registry setting. Lovely. Many many thanks for those who helped. Users here and ok - thanks to Eset. I like Eset and I really do not want to change my security soft. I do not want to reinstall my Win 10 either. :)

     

    I'm sorry to harp on but why aren't people backing up their systems? There's no real reason not to nowadays. It's not rocket science and the software is free. I find it unbelievable all this talk about reinstalling Windows, there's no need.

     

     

    I do backup, however I tend to delete old backups to save space, I actually backed up *after* an incorrect malware removal - bad luck eh? I only realised after a restart that it was borked...

     

    Shoot me! :P 

  6.  

     

    I have updated to pre release and have cleaner module 1112 (20150924), but the problem still persists.

     

    What value do you have in HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\(Default) ?

     

    %SystemRoot%\SysWow64\shell32.dll

     

     

     

    May I just add this, it may or may not help, but I have reinstalled Windows 10 thus correcting the issue and today installed Eset AV beta 9 and this is what I see in the above key:

     

    %SystemRoot%\system32\windows.storage.dll

     

    Is that correct for a Win 10 64bit system running Eset AV 9.0.141.0 (cleaner build 1112) ?

     

    For clarification, my sysyem is currently running fine with no folder issues etc.

  7. The question I need to ask is, is cleaner build 1112 expected to fix the issue for those currently having troubles, or as I suspect, is it expected to prevent the issue occurring in the first place?

     

    If it is the latter, then it seems those with the issue may have to bite the bullet and re-install, or wait for a fix at some point from M$ perhaps.

     

    Thanks in advance.

  8. Just as a matter of interest folks, can anyone confirm that this issue does not occur when using Eset AV and only seems linked to Eset Smart Security suite? I ask as I am giving Eset AV Beta 9 a whirl alongside Comodo firewall, I have made a full image of my drive, so I have a fallback should the issue reccur.

     

    Oh, and for information purposes, I too have the Nvidia driver for my GTX670 - version 355.82.

     

    However, on that note, I see that yesterday a new driver was released, 355.98 - guess I'll try this too and hope for the best.

     

    P.S. For what it's worth, I trialled Bitdefender 2016 briefly and disliked it, I need a working Eset, good luck all! 

     

    :)  :)  :) 

  9. Uninstalled ESS, no change. You guys are lookin in the wrong direction or some else just decided to screw up.

     

    Ken I appreciate that you are trying to help, but you are a little off the mark.

     

    The issue has page after page of posts on various websites pointing out that their icons no longer stay where put after a restart and the folder views are not saved either - example can't save as list view. keeps reverting to small/big icons whatever.

     

    Okay, the issue appears to be the result of Eset removing malware (as I said in an earlier post) following this removal the issue arises. 

     

    It is *not* just a general fault, the only time it happens is following the removal of malware, even potential malware as it was in my case.

     

    Furthermore, uninstalling Eset *after* the bug has been discovered does *not* fix the issue, it would appear something is corrupted during the malware removal (again as I said earlier)

     

    Thank you for your interest.

    :)  ;)  :P

  10. Right click on blank desktop space >>  Personalization  >> Themes >> Desktop Icons >> Uncheck allow themes to change desktop icons.

     

    I may have had this happen even though I use a solid color desktop.

     

    There is also a bat file around to rebuild the icon cache.

     

    Doesn't help, the issue seems to occur after ESS removes malware/potential malware - it's as if a registry entry is borked or removed completely upon said malware removal.

     

    As I said, it's a shame, as I'm now forced to look elsewhere. (temporarily - I hope)

  11. Hello, I recently installed the latest beta of Eset Smart Security (9.0.141.0) and all seemed well until I restarted my PC. I use Mailbird 2 as my email client and now every time I start Windows, or exit Mailbird and re-start it I get this - see attached screenshots.

     

    If I disable Eset protection, exit Mailbird, then restart it, the issue is gone, so it's ESS related.

     

     

    Please advise.

     

    post-1183-0-56521400-1440744540_thumb.pngpost-1183-0-33533900-1440744630_thumb.png

  12. Just Updated  v9.0.117.0 to v9.0,141.0

     

    Recent Component Updates:

     

    Virus signature database: 12156P (20150826)

    Rapid Response module: 6570 (20150826)

    HIPS support module: 1195 (20150826)

    Web content filter module: 1045 (20150824)

    Advanced antispam module: 2536P (20150826)

    Banking & payment protection module: 1036 (20150824)

     

    Windows 7 x64 Pro sp1 - Single reboot - no problems

    Thank you SCR, may I ask how you got that information? Or did you just compare old to new yourself?

×
×
  • Create New...