Jump to content

Reinstall doesn't work


Crunch
 Share

Recommended Posts

Hello,

I have uninstalled NOD32 with the uninstallertool.

But now I want to install NOD32 again.This doesn't work,I always get an error.

I have tried the live installer and eis_nt64.Nothing is working.

Can someone help me please?

Thank you.

Nod32.jpg

Link to comment
Share on other sites

17 hours ago, Marcos said:

Does running the installer with the "--avd-disable" parameter make a difference?

I don't understand this.What do you mean with avd disable?

Link to comment
Share on other sites

3 hours ago, Marcos said:

I mean to run the installer as follows:

eis_nt64.exe --avd-disable

When I add --avd-disable too the exe file,the file is no longer an exe file.

Link to comment
Share on other sites

  • Most Valued Members

first of all rename the file back to eis_nt64.exe  or better yet, redownload it if possible.

then open the start menu and type CMD, then select "open" from the right side, then in the window that opens type this c:\users\YOUR_USERNAME_HERE\downloads
(in the place of YOUR_USERNAME_HERE , type the username you have set your windows account. for example c:\users\john\downloads)

move the downloaded file in the Downloads folder and then type eis_nt64.exe --avd-disable

see the image for reference. hope i helped

 

Untitled.png

Link to comment
Share on other sites

  • Most Valued Members

also i would suggest to try again running the uninstall tool in the safe mode, run it a couple of times until it shows "no supported products found"

Link to comment
Share on other sites

17 hours ago, shocked said:

first of all rename the file back to eis_nt64.exe  or better yet, redownload it if possible.

then open the start menu and type CMD, then select "open" from the right side, then in the window that opens type this c:\users\YOUR_USERNAME_HERE\downloads
(in the place of YOUR_USERNAME_HERE , type the username you have set your windows account. for example c:\users\john\downloads)

move the downloaded file in the Downloads folder and then type eis_nt64.exe --avd-disable

see the image for reference. hope i helped

 

Untitled.png

This Solution worked to install again,but now I can't activate my NOD32.I have a valid activation code.

Capture.PNG.54d30b14bceabab31ce6237569f2ce28.PNG

Link to comment
Share on other sites

  • Administrators

Remove the following lines from C:\Windows\System32\drivers\etc\hosts and reboot the machine:

0.0.0.0 expire.eset.com
0.0.0.0 edf.eset.com

 

Link to comment
Share on other sites

26 minutes ago, Marcos said:

Remove the following lines from C:\Windows\System32\drivers\etc\hosts and reboot the machine:

0.0.0.0 expire.eset.com
0.0.0.0 edf.eset.com

 

That worked fine,thank you.

But now I get the following.

I use the dutch version of NOD32,sorry about that.

So I translated this.

"eset security status update in windows security center failed"

 

ESET.jpg

Link to comment
Share on other sites

1 hour ago, Marcos said:

Check if the Security Center service is running:

image.png

If it is, you might need to rebuild the WMI repository as per https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-rebuilding-the-wmi-repository/ba-p/373846

The security center servive is running.

That rebuilding of the WMI repository sounds like chinese to me.

Link to comment
Share on other sites

  • Most Valued Members

it's really easy. on the start menu type notepad and open the app that will appear on the results. then copy paste the contents on the website that Marcos suggested,

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

then save the file to the desktop for easy finding and rename it as repair.bat . before saving it on the "save as" dialog, make sure to change the file type to "ALL FILES" and not txt text file type. you can also right click the file later and rename it as "repair.bat" and remove the txt extension.

1.thumb.png.aa24a61be756f15d71b54cec5d1150ac.png

5.thumb.png.4116036018dc86c3a6830c1fc3486e22.png

7.thumb.png.86b9af418b6f1c2f8ea56a101922cdc8.png

Link to comment
Share on other sites

34 minutes ago, shocked said:

it's really easy. on the start menu type notepad and open the app that will appear on the results. then copy paste the contents on the website that Marcos suggested,

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

then save the file to the desktop for easy finding and rename it as repair.bat . before saving it on the "save as" dialog, make sure to change the file type to "ALL FILES" and not txt text file type. you can also right click the file later and rename it as "repair.bat" and remove the txt extension.

1.thumb.png.aa24a61be756f15d71b54cec5d1150ac.png

5.thumb.png.4116036018dc86c3a6830c1fc3486e22.png

7.thumb.png.86b9af418b6f1c2f8ea56a101922cdc8.png

Thanks for the reply.

I have tried this all,but still getting the messages.

ND1.jpg

ND2.jpg

Link to comment
Share on other sites

  • Most Valued Members
26 minutes ago, Crunch said:

Thanks for the reply.

I have tried this all,but still getting the messages.

ND1.jpg

ND2.jpg

When you uninstalled Eset did you uninstall normally or via the uninstall tool in safe mode? If not I'd recommend using the link bellow and running the tool, as it should remove all traces of Eset - it sounds like something might be leftover that is causing these issues

https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool

Link to comment
Share on other sites

21 minutes ago, peteyt said:

When you uninstalled Eset did you uninstall normally or via the uninstall tool in safe mode? If not I'd recommend using the link bellow and running the tool, as it should remove all traces of Eset - it sounds like something might be leftover that is causing these issues

https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool

I have used the uninstall tool in safe mode.

Link to comment
Share on other sites

  • ESET Staff

@Crunch Could you collect new set of logs? Hopefully we could find solution for those errors.

Edit: It would be great if you provide also process monitor log from boot stopped after the notifications start popping up. That could really help me with investigation.

Edited by JozefG
Link to comment
Share on other sites

On 9/29/2021 at 3:21 PM, JozefG said:

@Crunch Could you collect new set of logs? Hopefully we could find solution for those errors.

Edit: It would be great if you provide also process monitor log from boot stopped after the notifications start popping up. That could really help me with investigation.

Here are the new logs.

How can I get this?"It would be great if you provide also process monitor log from boot stopped after the notifications start popping up. That could really help me with investigation."

eav_logs.zip

Link to comment
Share on other sites

  • ESET Staff

@Crunch you can generate such log by following steps here https://support.eset.com/en/kb6308-using-process-monitor-to-create-log-files#boot_logs

It seems that you are experiencing very nasty issue :( API calls are returning ERROR_DISK_OPERATION_FAILED. Most probably due to failure during initialization of WSC service.

Link to comment
Share on other sites

  • Most Valued Members
1 hour ago, Crunch said:

I can't upload the log files because they are to big.

Try uploading them to a file sharing service. If you don't want anyone else to see them send the link in a PM

Link to comment
Share on other sites

21 hours ago, JozefG said:

@Crunch you can generate such log by following steps here https://support.eset.com/en/kb6308-using-process-monitor-to-create-log-files#boot_logs

It seems that you are experiencing very nasty issue :( API calls are returning ERROR_DISK_OPERATION_FAILED. Most probably due to failure during initialization of WSC service.

I have send you a pm with a downloadlink for the logfiles.

Link to comment
Share on other sites

  • ESET Staff

@Crunch thanks for the logs. Even though Bootlog.pml was corrupted/incorrectly closed. Logfile.pml contained the start of wscsvc :) So the issue in your case is that WSC cannot initialize its connection with WMI. Most probably due to fact that there is no WMI service running. Also there is no WMI Provider Host application running.

What does running this command from command prompt say?

wmic    /namespace:\\root\SecurityCenter2    Path    AntivirusProduct    GET    displayName,ProductState

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...