Jump to content

AVN

Members
  • Posts

    21
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by AVN

  1. I finally figured out what the problem was. Thanks to vkmaxx in this post :

    https://forum.eset.com/topic/3746-overlapped-io-operation-is-in-progress/#entry35035

    Ironically enough both issues ?seem to be related on two fronts?  ????????????????????

    Anyways, Completely uninstalling Eset, fully rebooting, changing the permissions to make the "C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\" folder "writable" for all users (Everyone), rebooting again, then re-installing finally did the trick :)

    You can always change the permissions back when you're done.

    :)

    On another note I wonder why the live installer isn't affected by the I/O issue.


    All in all a big mess that could have been avoided if Eset simply prompted the user to check that folder for the required permissions to install.   <_<


    EDIT:


    Just want to clarify, by permissions i meant security permissions and not read/write permissions

  2. All the beta versions of 9 worked for me good, it was only the final release candidate that had the problems. Don't forget all versions prior to 9 had the SSL filtering turned off by default, in 9 its turned on by default. So version 8 might of had the problem but I personally never had it because I never turned it on in 8 and prior!

     

    Problem still there with new build (349)

    Tried the new build here and got the same result.  So i uninstalled and wiped out eset completely then rebooted 4 times. Ran CCleaner and rebooted another few times.  .... Installed the Eset Smart Security 9 beta.... blah blah blah.... then force installed the Smart Security 9 beta.

     

    I don't get the error on boot anymore now BUT my definitions are not up to date and the actual certificate is still not in the TRCA.

    Also, when unchecking and rechecking the certificate option i get the error again.

     

    This issue has become exhausting.

  3. No, I don't think Eset know what the root cause of this problem is yet, I've never had this option turned on before with previous versions, so can't comment on weather the fault was long standing or not, but I was a beta tested from first release and never had the problem till the final release candidate!...the same goes for the lag and slowdown etc, that seems to have been pinpointed to a driver. (eamonm.sys)

    What was the last version (beta/alpha or not) that worked for you ?

    I also didn't have this issue back on eset 6? 7? (i forget which). But i did have some issues getting some SSL sites to load (i think it was in firefox mainly). I'm on 7x86 BTW with mostly all the current updates installed. (including defender)

  4. Yes when you uninstall Eset it automatically removes the certificate from that section!

     

    I still have the problem, Eset UK support failed to find the problem/answer even after remote assistance, so for now I have the whole ssl/tls protocol filtering turned off, and this was also stopping access to web sites which has already been documented elsewhere.

     

    I am hoping the new build when it finally arrives cures these problems!

     

    Oh I must just add.....it does in fact appear that the root certificate is in fact installed, regardless of the error message, so it is there!

    Do they know what the issue is ?

    Here is where we stand....

    I thought it might have been a permissions issue so I ran....

    secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose

    From the main admin account.(net user administrator /active:yes)   It spit out some issues ?which it said I could ignore?

     

    Then I ran.....

     

    @echo off
    title Resetting ACLs...
    
    setlocal
    
    echo.
    echo Determine whether we are on an 32 or 64 bit machine
    echo.
    
    if "%PROCESSOR_ARCHITECTURE%"=="x86" if "%PROCESSOR_ARCHITEW6432%"=="" goto x86
    
    set ProgramFilesPath=%ProgramFiles(x86)%
    
    goto startResetting
    
    :x86
    
    set ProgramFilesPath=%ProgramFiles%
    
    :startResetting
    
    echo.
    
    if exist "%ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe" goto filesExist
    
    echo ***ERROR*** - Could not find file %ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe. Double-check that SubInAcl is correctly installed and re-run this script.
    goto END
    
    :filesExist
    
    pushd "%ProgramFilesPath%\Windows Resource Kits\Tools"
    
    echo. 
    echo Resetting ACLs...
    echo (this may take several minutes to complete)
    echo. 
    echo IMPORTANT NOTE: For this script to run correctly, you must change
    echo the values named YOURUSERNAME to be the Windows user account that
    echo you are logged in with.
    echo.
    echo ==========================================================================
    echo. 
    echo. 
    subinacl.exe /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURPROFILE=f /setowner=administrators > %temp%\subinacl_output.txt
    echo. 
    echo. 
    subinacl.exe /keyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURPROFILE=f /setowner=administrators >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    subinacl.exe /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    subinacl.exe /keyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    subinacl.exe /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    subinacl.exe /keyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    echo System Drive...
    subinacl.exe /subdirectories %ProgramFilesPath%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    echo Windows Directory...
    subinacl.exe /subdirectories %windir%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt
    echo. 
    echo. 
    echo ==========================================================================
    echo. 
    echo FINISHED.
    echo. 
    echo Press any key to exit . . .
    pause >NUL
    
    popd
    
    :END
    
    endlocal
    

    As a batch file (Reset.CMD) ... Also in the main admin profile. (Without changing "YOURPROFILE" first).

    Both of which i soon imagined at the time needed to be run from the main admin profile and not Administrator.

    So I ended up doing that and as a repercussion one of the user accounts from the login screen disappeared.

    Following: hxxp://www.sevenforums.com/general-discussion/237456-user-accounts-missing-login-screen-control-panel-post2004864.html#post2004864

    I added the missing profile to the "user" group. (Which is a tricky thing to do if you don't know what you're doing.)

    That fixed the issue of the dissapearing profile, but now i'm back where I started.

    I'm wondering now if It could be a windows update (possibly KB3100213,KB3069762, or KB3072305), some other update, the installation then removal of spyhunter, or still a Ionewolf permissions issue that is causing the certificate issue.

     

    I should also note from what I recall I don't believe i had any problems with the certificate back on Eset 7.  ...Other than some webpage incompatibilities.

    I'll try a full uninstall and re-install this time and see what happens.....

  5. AVN,

     

    I had this issue a few weeks ago (the setting would still not make it work) and it turned out that I needed to uninstall ESS and manually remove the ESET root certificate as it was still left over on my machine from previous installations or was getting mismatched with ESS (even after using the uninstall tool).

    1. After uninstalling ESS (backup settings if you wish), press Win Key + R to open the run window.
    2. At this point, close any running programs, especially Internet Browsers, Email, etc.
    3. Enter 'certmgr.msc' and press OK (need Admin privileges)
    4. Find ESET's certificate under 'Trusted Root Certification Authorities', right click and Delete it.
    5. Restart your computer and reinstall ESS.
    6. Activate, update, and restart your computer once more.

    Since doing this, I haven't had any further error messages or issues with SSL or certificates, and actually solved my issues with ESS + IMAPS not working as well.

    I do not see the Eset certificate under TRCA , or anywhere else for that matter. Also, this did not fix the issue.

  6. Just as suspected it didn't help. I'm still getting the same error.
    note: i also made sure to reboot after making the registry modifications

     

    Log file - pastebin.com/raw.php?i=Mjg9guHh

     

    key used - {8DCE36CF-D28D-40B7-9C09-102FD0280BE0}

    Also tried key - {2E7EB14E-25A1-4A67-9EA6-C351CCD44990}
    And got the same result.

    Just to be clear yet again, I'm still getting the same error nothing has helped or has even narrowed down for me what the problem is.

  7.  

    3 things stand out to me.

    MSI (c) (90:A8) [20:43:43:440]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\Andrea\Downloads\ess_nt32_ENU.msi' against software restriction policyMSI (c) (90:A8) [20:43:43:440]: SOFTWARE RESTRICTION POLICY: C:\Users\Andrea\Downloads\ess_nt32_ENU.msi has a digital signatureMSI (c) (90:A8) [20:43:44:697]: SOFTWARE RESTRICTION POLICY: C:\Users\Andrea\Downloads\ess_nt32_ENU.msi is permitted to run at the 'unrestricted' authorization level.

    and

    Info 2898.For DlgStdFont textstyle, the system created a 'Tahoma' font, in 1 character set, of 13 pixels height.Info 2898.For UiFont_Bigger textstyle, the system created a 'Verdana' font, in 1 character set, of 20 pixels height.DEBUG: Error 2826:  Control BottomLine on dialog PrepareDlg extends beyond the boundaries of the dialog to the right by 3 pixelsThe installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: PrepareDlg, BottomLine, to the rightAction ended 20:43:46: PrepareDlg. Return value 1.

    Also

    === Logging stopped: 12/8/2014 20:51:43 ===MSI (c) (90:A8) [20:51:43:646]: Note: 1: 1707 MSI (c) (90:A8) [20:51:43:646]: Product: ESET Smart Security -- Installation completed successfully.MSI (c) (90:A8) [20:51:43:646]: Windows Installer installed the product. Product Name: ESET Smart Security. Product Version: 8.0.301.0. Product Language: 1033. Manufacturer: ESET, spol s r. o.. Installation success or error status: 0.MSI (c) (90:A8) [20:51:43:650]: Grabbed execution mutex.MSI (c) (90:A8) [20:51:43:650]: Cleaning up uninstalled install packages, if any existMSI (c) (90:A8) [20:51:43:684]: MainEngineThread is returning 0=== Verbose logging stopped: 12/8/2014  20:51:43 ===

    What 3 things exactly stand out there ?

     

     

    According to this article hxxp://support.microsoft.com/kb/2918614

    You could try a manual fix with the registry.

    Let us know if this helps.

    I will try this but i'm doubtful it will help.

  8. Hello,

     

    My name is Jeff I work with ESET Tech Support.

     

    I have ran into this issue a few times and was able to fix it by implementing the following steps:

     

    - Go to start, and in the search bar, type Run. Next select Run and this should bring up the Run Box. 

     

    - Next, drag your ESET install file into the run box.  It will convert it to the path that it is stored on eg: C:\User1\Desktop\eavh_nt64_enu.msi

     

    - Once you have your path to the install file in the run box, press space then enter /lvx* install.log

     

    - So what you will have in the run box, for example, is C:\User1\Desktop\eavh_nt64_enu.msi /lvx* install.log

     

    - Press the OK button and the Install should then execute and finish normally.

     

    Thus far, adding this switch has resolved the Overlapped I/O in progress error when I have used it.

     

    Please let me know if this resolves your issue.

     

    Thank you for choosing ESET Security Products,

     

    Jeffrey

    ESET Business Support

    North America

     

     

    AVN, thanks for trying the KB first. Your feedback on the success or failure of Jeffrey's steps above will help us update our KB content. 

    This did NOT fix the issue for me.

    I still get the same error.

    Here is the contents of the log file.

    pastebin.com/raw.php?i=nd0vhjqN

  9. Can anyone help i'm getting this error when installing the latest version “Overlapped I/O operation is in progress” , I tried uninstalling the KB2918614 update as well as installing the KB300988 hotfix but i'm still getting the error. I was able to get the KB300988 hotfix to install fine but i still cannot install a msi package. I still get the overlapped error.

    I even tried creating a new windows profile but that didn't help either

    I do have update
    KB3008627 installed , i also tried removing that update and tried installing as well as reinstalling that update and installing. That didn't help either. Same error every time.

×
×
  • Create New...