Reinstall doesn't work

[Crunch 0]

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.

[Marcos 4,703]

Could you please choose English before taking a screen shot of the error so that we see it in English? Also please provide logs collected with ESET Log Collector.

[Crunch 0]

This is what I get when I want to install NOD32.

I have included the logs.

ELC_logs.zip

[Marcos 4,703]

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

[Crunch 0]

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?

[Marcos 4,703]

I mean to run the installer as follows:

eis_nt64.exe --avd-disable

[Crunch 0]

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.

[shocked 60]

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

 

[shocked 60]

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"

[Crunch 0]

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

 

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

[Marcos 4,703]

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

 

[Crunch 0]

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"

[Marcos 4,703]

Check if the Security Center service is running:

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

[Crunch 0]

1 hour ago, Marcos said:

Check if the Security Center service is running:

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.

[shocked 60]

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.

[Crunch 0]

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.

Thanks for the reply.

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

[peteyt 359]

26 minutes ago, Crunch said:

Thanks for the reply.

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

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

[Crunch 0]

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.

[JozefG 6]

@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 September 29, 2021 by JozefG

[Crunch 0]

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

[JozefG 6]

@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.

[Crunch 0]

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

[peteyt 359]

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

[Crunch 0]

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.

[JozefG 6]

@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