Install/Config help for Vista

Hi All:

I am just playing with the latest vista build. Everything is working fine. I installed nod32 (2.70.23) (licensed user), and it installed with no problems.

As soon as I try to run an on-demand scan, a pop up appears indicating it could not run, tries to find a solution on line, and that's it. Nod32 updates just fine, and all else seems ok. Just can't do a manual scan of any kind.

I saw some instuctions on-line that seem verbose. I have the default windows defender, firewall and the user account control (uac) running. On win 98 and xp nod32 install was seamless. Are there other steps necessary with vista?

Any help to get nod32 working properly would be appreciated.

 

what happens if u disabled UAC and then run a scan?

 

wsfuser:

Disabled uac plus windows firewall plus defender, nod32 still would not run.

 

im using Kaspersky and not NOD32 so i cant help much, but im sure someone will be able to.

 

Hello,

Are you logged in as an administrator?

Which build and edition of Microsoft Windows Vista is the problem occurring with?

Was the computer upgraded from a previous build or edition of Windows Vista, or is this a clean install of the operating system?

Is there any other security software installed on the computer?

Regards,

Aryeh Goretsky

 

Aryeh:

Sent a "ticket" yesterday via eset website with all info. Will be happy to review though:

Vista Beta 2 5384
Clean install
Windows Defender 1.1593.0,
Windows Firewall.

Logged in as administrator? As far as I know, my username was setup as the administrator. Indicated as such in control panel.

Based on crash log, seems like it may be related to MS Office pro 2007.

Log:

Problem signature
Problem Event Name: APPCRASH
Application Name: nod32.exe
Application Version: 2.70.23.0
Application Timestamp: 457eaed5
Fault Module Name: OLKFSTUB.DLL_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 445aa753
Exception Code: c0000005
Exception Offset: 386f444f
OS Version: 6.0.5384.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 64a7
Additional Information 2: 52f34e409edde6bf0f546485075a6cfd
Additional Information 3: 73ec
Additional Information 4: 3cfe623990e9ba67b4f708dcc2ba7934

I can run a scheduled scan OK. Cannot run a manual in-depth or local scan without receiving a message that the nod32 on demand scanner has stopped working.

Haven't heard anything back as of today.

Thanks.

 

Does running "nod32.exe /mapi- /scanmem-" make a difference?

 

Aryeh:

Please correct me if I did this incorrectly.

In the run box:

C:\Program Files\ESET\nod32.exe /mapi- /scanmem-

Hit Run:

Result:

Same as before

NOD32 on demand scanner has stopped working

I also have the User Account Control turned off. Windows Firewall and Defender, whether on or off, still give the same result.

Thanks.

 

Aryeh:

Did some more "digging" on this.

When I go into the eset folder and double click on the nod32 icon I get this message:

Microsoft Outlook

Either there is no default mail client or the current mail client cannot fulfill the messaging request.

Please run Microsoft Outlook and set it as the default mail client.

OK, I checked and rechecked and Outlook is definitely set as the default mail client. However, when I go into Vista Program Defaults, it shows that Windows Mail (Outlook Express replacement), is the default mail application. It won't even give me the option to set Outlook in the Default Programs option.

Maybe your group can duplicate this, and if so, that is what may be causing the problem?

Thanks.

 

Aryeh:

Just wanted to drop you a quick note that this is fixed. For other as an FYI, after installing MS Office Pro 2007, (at least on my install), it left the windows mail, (old express), as the default, not outlook. After changing all this, nod32 started working.

Thanks.

 

Hello,

Thank you for letting me know.

One thing to keep in mind is that Microsoft Windows Vista Beta 2 (Build 5384) is an older build of Vista and not a code-complete version of the operating system. Build 6000 was released in November 2006, and that is the build ESET plans on providing mainstream support for. Also, because Build 5384 is a beta version and not a final version, the amount of support ESET can provide is very limited and will decrease when Build 6000 becomes available in the retail channel at the end of January 2007 (it is already available on MSDN).


Regards,

Aryeh Goretsky