NOD32 breaks ActiveX?

[csmager]

I've been trying to get various things to work over the last few days that have involved ActiveX - winks on MSN require Flash which is installed as an ActiveX plugin, MSN Games require plugins, Egg Money Manager, ths list goes on.

It came to my attention that ActiveX didn't work. It just pops up the box, you click install, and then nothing happened! I did some googling, and found a few other people with the same problem, and thought it might be SP2 related - and it may be....

I formatted, reinstalled a slipstreamed SP2 and ActiveX worked. I then decided it must be some software, so I installed pieces one by one and found it was NOD32 causing the problem. I did more googling and found a few others with the problem. One guy cured it by going back to SP1. But a friend of mine runs NOD32 with SP2 with no problems... so I'm confused - I have emailed Eset though.

Could anyone with NOD32/SP2 try this in IE:

http://www.pcpitstop.com/testax.asp

And any suggestions/solutions welcome!

[ronjor]

This is what I get with IE at the link above. It is not a problem for me, that's the way I like it.

Test Your ActiveX Installation
This page tests whether you have your browser properly configured to download, authenticate, install, and display ActiveX controls, and manipulate them with JavaScript.

When prompted with a certificate, please accept it. The current date and time should appear below:



If you see the current date and time displayed above, congratulations! ActiveX and scripting are working properly. (If you see a date and time but it isn't the right time, your PC's clock is set wrong! Double-click the time in the system tray to correct it.)

If, instead of the time, you see a box with a small x in it, either:

ActiveX is not supported: Use Internet Explorer to view the site.
ActiveX is not enabled: See these instructions to enable ActiveX.
You didn't accept the certificate: You must click Yes on the security certificate to load the ActiveX control.
You are using an ad blocker, popup stopper, or firewall that blocks ActiveX: Disable these utilities to see if they are the cause.
Your system has spyware installed or a virus that interferes with ActiveX: Scan for spyware with a product like Pest Patrol or Panda, available in our store.
If you see a blank space, ActiveX is probably working properly, but not scripting. Check your security settings for scripting.

If you see the message ActiveX is not supported, then your browser doesn't recognize ActiveX at all. Netscape, Opera, or other browsers usually do not support ActiveX.

When you think you've corrected any problem you are having with this, simply refresh the page [press F5] to try again.

[Gauthreau]

It works in mine. I had to click to install.

Neil

[csmager]

-{ Quote: "This is what I get with IE at the link above. It is not a problem for me, that's the way I like it." }-

I'm not entirely sure what you're saying - does it work or not? I don't think posting the content of the page really helped!

I get the dialog asking me if i want to install, i click install and nothing happens. A red x appears to signify it didn't work. If anyone has any idea as to why this happens, that'd be great.

[Gauthreau]

Some people prefer to have ActiveX disabled because of the risk it presents in terms of access to your computer or viruses etc. I'm not too sure why your's isn't working though.

Neil

[rumpstah]

Hi csmager:

Did you follow the instructions here?

http://www.pcpitstop.com/faq/security.asp

NOD32 by itself does not block ActiveX controls unless they are malicious (or possibly malicious). Since you are not receiving an IMON or AMON alert, this presumably is caused by the security configuration of IE.

Drop us a note if this helps! ;)

-{ Quote: "I'm not entirely sure what you're saying - does it work or not? I don't think posting the content of the page really helped!

I get the dialog asking me if i want to install, i click install and nothing happens. A red x appears to signify it didn't work. If anyone has any idea as to why this happens, that'd be great." }-

[csmager]

I've followed every piece of advice I can find for configuring IE and the like - nothing helps.

All I know is a fresh install of XP SP2 works completely fine.

Installing NOD32 breaks ActiveX.

This happens on 3 out of 3 of my pcs. And it does appear I'm not alone.

[Blackspear]

-{ Quote: "I've followed every piece of advice I can find for configuring IE and the like - nothing helps.

All I know is a fresh install of XP SP2 works completely fine.

Installing NOD32 breaks ActiveX.

This happens on 3 out of 3 of my pcs. And it does appear I'm not alone." }-With this unusual issue can you please send an email to support@nod32.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

Cheers ;D

[Phil_S]

I have also been suffering the same problem as csmager, and have been corresponding with him regarding it on another forum.

I first noticed the problem a couple of weeks ago, having bought an IP Camera which needs to install an ActiveX control to enable configuration through IE. I couldn't get the control to install. I then found that I couldn't get any new ActiveX controls to install, although those that were already in my Downloaded Program Files folder still worked normally (including Windows Update). I assume that the problem must have existed since updating to XP SP2, though I hadn't noticed it before, as I hadn't needed or tried to install any other ActiveX controls.

After trying many things, including re-registering crypto dlls and reinstalling security certificates, I decided to format and re-install XP Pro. As soon as I was up and running (on SP1) I connected to my IP Camera and installed the ActiveX control with no problem. I found that other ActiveX controls would download and install, so thought the problem was solved.

Then I let Windows Update bring me back to SP2 and found that I was prevented from installing any ActiveX controls again, although those already installed worked fine, so I assumed that the problem was being caused by SP2 somehow.

The symptoms are that when I go to a page that wants to install an ActiveX control, I get the IE Information Bar notification. I click on that to select Install, and get the box giving me the option to Install or Cancel - all perfectly normal SP2 behaviour so far. As soon as I click on Install however, the box closes and I just get a red cross on the page where the graphic placeholder icon was displayed, and nothing gets downloaded.

I haven't actually found anything whilst searching Microsoft KB that completely fits my problem, but did find out that if an ActiveX download fails, a log file is created in the Temporary Internet files folder, called
"?CodeDownloadErrorLog!name={<CLSID of failed component>}"

A Code Download Error Log Viewer can be obtained from Microsoft at http://download.microsoft.com/download/6/8/3/683DB9FE-8D61-4A3C-B7B8-3169FF70AE9F/cdllogvw.exe which allows viewing of the error logs created when an activex install fails. I found that every failure had the same error 80004005, as per the below log entry:

--------------------------------------------------------------------------
Code Download Error: (hr = 80004005) Unspecified error

Operation failed. Detailed Information:
CodeBase: http://www.pcpitstop.com/mhLbl.cab
CLSID: {9732FB42-C321-11D1-836F-00A0C993F125}
Extension:
Type:

LOG: Reporting Code Download Completion: (hr:80004005 (FAILED), CLASSID: 9732fb42..., szCODE:(http://www.pcpitstop.com/mhLbl.cab), MainType:(null), MainExt:(null))
--- Detailed Error Log Follows ---
LOG: Download OnStopBinding called (hrStatus = 0 / hrResponseHdr = 0).
LOG: URL Download Complete: hrStatus:0, hrOSB:80004005, hrResponseHdr:0, URL:(http://www.pcpitstop.com/mhLbl.cab)
LOG: Reporting Code Download Completion: (hr:80004005 (FAILED), CLASSID: 9732fb42..., szCODE:(http://www.pcpitstop.com/mhLbl.cab), MainType:(null), MainExt:(null))
--------------------------------------------------------------------------

According to Microsoft, this error code indicates that the data cannot be accessed. The error can be paraphrased as "I could not access your data for some reason." The log above relates to the date/time test control at www.pcpitstop.com, but the erro message and code is identical for all installation attempts from varying sources.

Having backed out to SP1 again, the problem was resolved, but on returning to SP2, downloading of activex controls again stops working. The problem is entirely reproducible on my machine.

I know that csmager has the same problem (and the same error code) on at least three of four machines. The similarities are that we are both running XP Pro SP2, and both running our machines on small private LANs behind routers running NAT. We have both experimented with bypassing the routers and can rule them out as a cause of the problem.

The other similarity between us is that we are both running NOD. I have experimented with disabling IMON, but found that had no effect on the problem. csmager has now informed me however that he has found that completely removing NOD from his machine allows ActiveX controls to download and install, and that re-installing NOD reintroduces the problem.

I haven't yet had chance to try this on my machine, but I have no reason to doubt what he is saying. Once I have tried it I will of course report back here.

That is why csmager is asking any other NOD users running SP2 (preferably XP Pro) to try the activex test download at http://www.pcpitstop.com/testax.asp to see if the problem is reproducible. The control is quite safe and simply inserts the current date and time in the relevant web page (if it works on your machine!).

Once you have completed the test, the control can easily be removed if desired by opening the Tools/Internet Options menu in IE, selecting General/Temporary Internet Files/Settings/View Objects, right clicking on the entry for "mhLabel Class" and selecting Remove.

I would reiterate that unless you have consciously attempted to download an ActiveX control since installing SP2, you would not be aware even if you do have the problem.

I just have a niggle in the back of my mind. I know that NOD shouldn't interfere with ActiveX controls unless they are malicious and detected in its database, but it will be checking them as they download. If NOD's intervention is causing the data to be delayed or not presented as the OS expects, could that cause IE to log a download error?

[flyrfan111]

Works fine here, XP SP2, NOD set to max settings. Perhaps it is your browser or firewall settings.

[anotherjack]

Add me to the "no problems found here" group. Fresh SP2 install, already had NOD installed with tight settings before I ran across this thread. Had to run IE (blech) to test it, since Opera doesn't do ActiveX, but the control installed just fine and ran properly.

[spy1]

It's definitely not NOD32 causing this - check out the screenshots (there'll be three or four in separate posts due to the lovely fact that you can't post more than one attachment per post here). Pete

[spy1]

Second one.

[spy1]

Number 3

[spy1]

Number 4

[spy1]

Number 5 - This is the section of Tools/Internet Options "Security" tab/"Internet" Zone/"Custom Level" you need to look at (if indeed, you're using a "Custom"ized level - if you're at the default, that's probably what's killing you right there). Sorry that took so long - I'm running behind Tor/Privoxy/SocksCap and things are slower than all get-out right now.

Would some of you people that can do so please consider running a Tor server? Pete

[csmager]

Sorry if I'm being somewhat dense here, but how on earth do those 4 posts prove that "It's definitely not NOD32 causing this"?

That seems completely unfounded to me. I'm not a complete dunce, I have checked and triple checked my security settings, and even when there isn't a single piece of software on 3 different PCs, except NOD32, ActiveX controls won't install. Uninstalling NOD32 causes ActiveX installs to work again.

[Blackspear]

-{ Quote: "...even when there isn't a single piece of software on 3 different PCs, except NOD32, ActiveX controls won't install. Uninstalling NOD32 causes ActiveX installs to work again." }-Did you send an email to support@nod32.com regarding this issue?

Cheers ;D

[Phil_S]

Right, this is what I have done this morning:

1) Completely wiped, reformatted and installed XP Pro SP1 on my C: drive.

ActiveX downloads fully working.

2) Installed SP2 from SP2 Network Update KB835935

ActiveX downloads fully working

3) Installed the following updates one at a time, rebooting after each update and testing:

KB886185 Critical Update for Windows XP
KB834707 Cumulative Security Update for IE XP SP2
KB887797 Cumulative Update for OE Windows XP

System now fully updated according to Windows Update.

ActiveX downloads still fully working.

Installed NOD32 2.12.3 - Amon starting automatically, HTTP checking enabled and IMON registered to system, DMON disabled (I use OpenOffice).

Selected option to reboot later at the end of the install.

Tested ActiveX - broken. Error 80004005, exactly as before.

Rebooted. Tested ActiveX - broken. Error 80004005, exactly as before.

Uninstalled NOD. Rebooted. ActiveX downloads fully working.

Re-installed NOD. Rebooted. ActiveX broken.

Sure looks like a NOD conflict to me :( Why it only seems to affect certain systems is a mystery.

I will also email Eset with a link to this thread. I wanted to do my own tests as above before sending a support request though, as up to now I wasn't completely certain.

Edit: Should also add that I had SP2 firewall totally disabled during these tests, and all IE settings at default.

==========================================================
NOD32 Antivirus System information
Virus signature database version: 1.962 (20041231)
Dated: 31 December 2004
Virus signature database build: 5117

Information on other scanner support parts
Advanced heuristics module version: 1.011 (20041126)
Advanced heuristics module build: 1067
Internet filter version: 1.002 (20040708 )
Internet filter build: 1013
Archive support module version: 1.025 (20041221)
Archive support module build version: 1106

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.3
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.3
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.3

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 512 MB
Processor: Intel(R) Pentium(R) 4 CPU 2.66GHz (2672 MHz)

[Blackspear]

-{ Quote: "I will also email Eset with a link to this thread. I wanted to do my own tests as above before sending a support request though, as up to now I wasn't completely certain." }-Thanks Phil, appreciated, and good to see the thoroughness of your testing...

Cheers ;D

[Phil_S]

-{ Quote: "Thanks Phil, appreciated, and good to see the thoroughness of your testing...

Cheers ;D" }-

Couple more tests I've tried in the meantime:

IMON running, HTTP checking disabled, ActiveX still broken.

IMON disabled, rebooted to remove NOD from the LSP chain, ActiveX still broken (had tried this last week - the first time I wiped and reformatted my disk :( - but wanted to make sure.

So it seems to me to be something to do with the way NOD installs itself on my system, and not a conflict with the http scanner or Internet settings.

Phil - currently in the process of reloading all my software for the second time in a week!

[csmager]

Glad you found the same as me! Hopefully Eset will reply to the few emails they have.... and I really hope they can reproduce the problem!

[spy1]

-{ Quote: "Sorry if I'm being somewhat dense here, but how on earth do those 4 posts prove that "It's definitely not NOD32 causing this"?." }-

Guess I should have clarified - it's definitely not NOD32 causing what you're seeing here. The screenshots plainly show that it's IE that's throwing up the ActiveX warning (first screenshot). That's IE doing the warning. When I clicked on that warning, it told me again that it was a Windows Explorer security warning (second screen shot). When I clicked to "Install", I got a warning from SBS&D's "Resident" protection about it (third screenshot), which I "Allow change"d on. The ActiveX control successfully installed, as shown by the fourth screenshot.

-{ Quote: "I'm not a complete dunce," }-

(Sigh) I never implied that you were. If you somehow got that impression, you're mistaken (but I'll apologize anyway).

The only reason I took the time to do all that was because I, too, am running Win XP Pro and NOD32 (same specs as yours re: NOD) - and I'm not having the problem you're having. I verified that by going through all the steps shown in the screenshots.

Since your problem evidently stems from something not seen here on my machine, I'll happily bow out and let you get it resolved.

Good luck. Pete

[csmager]

-{ Quote: "Guess I should have clarified - it's definitely not NOD32 causing what you're seeing here. The screenshots plainly show that it's IE that's throwing up the ActiveX warning (first screenshot). That's IE doing the warning. When I clicked on that warning, it told me again that it was a Windows Explorer security warning (second screen shot). When I clicked to "Install", I got a warning from SBS&D's "Resident" protection about it (third screenshot), which I "Allow change"d on. The ActiveX control successfully installed, as shown by the fourth screenshot." }-
I'm still not entirely convinced I know what you're getting at here, but my summation of it so far is, instead of your four posts, you could've written "It works fine for me", as it indeed seems to for some.

I think everyone knows what *should* happen, this being evident in the fact that some of us realise it isn't functioning correctly with NOD32 being sited as the cause of this.

[Bandicoot]

Hello csmager,

Well I have to agree with some of the other posters here, in that I haven't found any issues or problems regarding installing ActiveX type programmes and I'm also running XP SP2.

However, the problem might be caused by DMON which scans ActiveX elements. I know Phil_S said he disabled DMON but I don't think it's truly disabled when you do this. Even re-installing and not having DMON included as a default scanning module (can be done in Advanced and Expert modes of installation) may not totally stop DMON from being present.

I suggest you download this file from here: http:\\eset.zftp.com/ntstden.nup and save it somewhere safe.

Next, uninstall NOD32 and reboot. Now locate the file you've downloaded and copy it to the Eset Install Directory. You are in fact replacing a file (ntstden.nup) so you may want to backup the original. Personally, I wouldn't bother because if you wanted to revert back to your existing setup, you could simply download a fresh installer, but that's up to you.

Now run the setup.exe from the same directory, to re-install NOD32. Now, if all goes according to plan, you will have no DMON installed whatsoever.

How do ActiveX apps behave now?

Bandicoot (Eset).
::)

[csmager]

I really do think you've solved it - or at least found a workable solution!

What exactly is the install file? Just a copy of the program with the DMON module removed? Will I have to use this file everytime I have to install NOD32? Because if so, I'd better keep it somewhere very safe!

I know this is a solution, but ideally it'd be nice if it worked 'out of the box' as it were - can you think of any reason some people are getting unresolveable issues with this and some aren't?

Thanks again

Charlie

[Phil_S]

Well done Mr. Coot, you've solved it ;D ;D ;D

I had installed NOD in expert mode and excluded DMON, but like you said, it doesn't completely remove DMON as the icon is still visible in the contol centre.

Anyway, replacing the file you suggested has fixed it. I guess I'd better put a copy of that somewhere very safe, along with your instructions.

Thank you very much. I'm now going off to try and grow some hair again :)

[jmc777]

Fixed it for me too! :)

[Hexaguano]

Completely removing DMON worked for me as well (WinXP SP2). I wouldn't have known I had a problem until I read this post. Thanks!

So, will the next release fix this problem or will we have to get another "special" file ?

[Bandicoot]

Wa-heeeeeey.......excellent news!

I'll ask the developers whether a fix can be added to the next PCU or not. For the moment, hang on to the .nup file that I sent (to Phil_S and csmager) and if anybody else needs this file, please contact me at support@eset.com and I'll gladly send you a copy.

I'll report back here as and when I get some information from my techno chums.

Bandicoot. ;D

[Bandicoot]

First of all, could I ask Phil_S, csmager and anybody else with the same issues regarding ActiveX, to send a HijackThis log in to Eset? When doing so, could you tell us what type of CPU you have on your machine and whether you're running XP SP2?

(Here's a link for HijackThis: http://www.spywareinfoforum.com/%7Emerijn/downloads.html

Please send logs and info to support@eset.com

Thanks very much to everybody.
Bandicoot. ;D

[Phil_S]

Hi Bandicoot,

Log sent :)

Many thanks,

Phil

[wpritch]

-{ Quote: "Sorry if I'm being somewhat dense here, but how on earth do those 4 posts prove that "It's definitely not NOD32 causing this"?

That seems completely unfounded to me. I'm not a complete dunce, I have checked and triple checked my security settings, and even when there isn't a single piece of software on 3 different PCs, except NOD32, ActiveX controls won't install. Uninstalling NOD32 causes ActiveX installs to work again." }-


I have tried the web site mentioned before. Sp2 with IE at default settings, and NOD32 at max settings....no problem in installing the component.

[Phil_S]

-{ Quote: "I have tried the web site mentioned before. Sp2 with IE at default settings, and NOD32 at max settings....no problem in installing the component." }-

For you, maybe not, but for those of us affected by this problem it has been necessary to replace one of the NOD installation files with a dummy file that has the effect of completely removing DMON from the NOD installation.

Why this is necessary, and why it only affects some machines is something that Eset are investigating, but I can assure you having applied Eset's fix that NOD (specifically DMON) was causing the problem.

[S!x]

Active X is just a set of rules on how programs will share information...

So if this is NOD 32 (DMON) causing this, why isn't it the same for everyone with the same configuration?...(NOD,SP2, using IE) The rule applied would be the same for everybody.

Maybe DMON is doing it's job? ... possibly those Active x controls may not be safe to run on your PC for one reason or another? ...

Definantly a strange deal ... seems it's about a 50/50 chance of being affected.

Test works fine on mine running IE, SP2, NOD32 ...DMON running strong. Although i had to weaken mi IE security settings ...to allow Active X controls to run.

(A.) An ActiveX control is similar to a Java applet. Unlike Java applets, however, ActiveX controls have full access to the Windows operating system.)

(B.) An ActiveX control can be automatically downloaded and executed by any Web browser.)

i usually don't allow any Active X controls to run at all ... not good for security.

NOD32 Antivirus System information
Virus signature database version: 1.964 (20050104)
Dated: Tuesday, January 04, 2005
Virus signature database build: 5124

Information on other scanner support parts
Advanced heuristics module version: 1.011 (20041126)
Advanced heuristics module build: 1067
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.025 (20041221)
Archive support module build version: 1106

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.4
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.4
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.4

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 512 MB
Processor: Intel(R) Pentium(R) 4 CPU 2.53GHz (2545 MHz)

[spy1]

Could it possibly be related to whether it's simply a stand-alone computer or a LAN? Or indeed to whether or not you've even got M$ Office installed? (I don't). Pete

[csmager]

-{ Quote: "So if this is NOD 32 (DMON) causing this, why isn't it the same for everyone with the same configuration?...(NOD,SP2, using IE) The rule applied would be the same for everybody.

Maybe DMON is doing it's job? ... possibly those Active x controls may not be safe to run on your PC for one reason or another? ..." }-
But it does this when DMON is supposed to be disabled? And it does this on ActiveX controls that are perfectly safe - actually, it does it on every ActiveX control!

-{ Quote: "Could it possibly be related to whether it's simply a stand-alone computer or a LAN? Or indeed to whether or not you've even got M$ Office installed? (I don't).
Pete" }-
All my PCs are on a Windows 2003 Domain behind a NAT ADSL router, and they all have the same problem. I did try completely reinstalliing windows and not joining the domain, still it didn't work. I also tried using a dialup connection, and it still didn't work - although I probably did this one while joined to the domain.

Office 2003 is installed, but it wasn't on the completely blank installation.

[aliwiseman]

Hi there. Not sure if this may help but i'll put it anyway.

Nod32 is commonly picked upon as a prog that conflicts with many things. This is quiet often resolved by the order of how things are installed... eg uninstall Nod, install app, re-install nod, or vice versa.

I've encountered this with a few things when using Nod, not least Spysweeper, which throws a fit and disables more shields than u can shake a stick at!

Following this with a curious air as i've seen nod mentioned enuff to think maybe its easier to do without.

Alistair Wiseman


Alistair Wiseman Homepage (http://geocities.com/aliwiseman1974)

[ronjor]

Nod is the least intrusive antivirus program I have ever used. I have used a lot of them over a ten year period.
It is a fact, any antivirus program can have conflicts on different machine configurations.

[Phil_S]

-{ Quote: "Nod32 is commonly picked upon as a prog that conflicts with many things. This is quiet often resolved by the order of how things are installed... eg uninstall Nod, install app, re-install nod, or vice versa.
" }-

If you read through the thread, you'll see that we both did some fairly extensive testing before suggesting NOD as being related to the problem.

I for one had been applying MSKB tweaks and altering registry settings for over two weeks before exhausting ideas. I then completely wiped everything and started again from scratch.

It's difficult to suggest how to install things differently when I came to the conclusion that NOD was implicated after completely wiping my machine, reformatting and installing only the OS before installing NOD. Should I have installed NOD before I put an OS on my machine ???

The fact is that on my machine with only XP Pro installed straight off disk and SP2 including all available updates applied, activeX worked. As soon as I installed NOD it stopped. As soon as I applied the fix suggested by Bandicoot (who is an Eset employee) the problem was resolved. There were no other apps on my machine to conflict with NOD.

I am not knocking NOD at all. I think it is the best AV around, otherwise I wouldn't be using it. I posted in the forum having identified an issue that was a real problem for me, and having become certain through logical testing that NOD was somehow involved. I am also very impressed with Eset's support, which once the problem was identified, could not have been quicker.

The fact is that there are thousands of different permutations of computers, hardware and software configuration out there, and conflicts are to be expected. That is one reason why both hardware and software vendors update their wares and issue patches. MSKB for example is full of solutions for problems that affect some, but not all users of MS software.

I am not blaming NOD. I am not saying NOD is necessarily the component at fault, but there is a conflict between the current version of NOD and my machine. Eset have provided a solution which overcomes this, and they have asked for, and been given, further information in an effort to locate the problem and possibly obtain a more permanent solution. As an end user, I could not ask for more in the way of support than I have been given.

I have been using computers for long enough to know that just because something works on one machine doesn't guarantee that it will work on every other. An assumption that "because X works for me, your problem cannot be X" can only be an assumption, no more, no less. It is helpful to know that other people may not be experiencing the same problem, but it is not helpful to be told that because they are not experiencing the same problem, I must be mistaken.

As a result of this thread it can be extrapolated that a great majority of users are not experiencing any problem with this issue. It is also apparent that a minority, maybe a very small minority, are. I only came across csmager after days spent searching the Internet and newsgroups trying to find if anyone was experiencing similar issues to me. Since posting our findings here, at least one other person (who has contributed to this thread) has found that he also had the same problem, which until he attempted the test, he had been completely unaware of, and he has also overcome the problem by applying Eset's fix. There may be others who also have the same issue, but are still unaware of it, because they don't subscribe to this forum, haven't read this thread, or haven't encountered a situation wher they needed to install a particular activex control to enable a new item of hardware, and found that to be impossible.

From the methological testing that I have carried out to verify this problem before I even contemplated posting anything here, I am certain that either:

1) There is a conflict between NOD 2.12.3 and my machine, which could well be caused by either the harware configuration of my machine, or the way in which it is networked, or:

2) There is a conflict between NOD 2.12.3 and the extremely rare and unique version of Windows XP Pro that Bill Gates wrote specially for me and a small handful of other (un?)lucky people ;)

I am not sure what more is to be gained by continuing discussions on this issue. A small minority of us had a problem. We identified the circumstances in which in manifested itself to us, and we raised it. Bandicoot, bless him, identified a solution. Problem resolved. The only thing I can see as being worthy of any further mention is if Eset or anyone else manages to pinpoint the exact nature and cause of our problem, and hopefully come up with a more permanent solution.

[Phil_S]

-{ Quote: "But it does this when DMON is supposed to be disabled? And it does this on ActiveX controls that are perfectly safe - actually, it does it on every ActiveX control!" }-

Even the one that controls Windows Update!

-{ Quote: "All my PCs are on a Windows 2003 Domain behind a NAT ADSL router, and they all have the same problem. I did try completely reinstalliing windows and not joining the domain, still it didn't work. I also tried using a dialup connection, and it still didn't work - although I probably did this one while joined to the domain.

Office 2003 is installed, but it wasn't on the completely blank installation." }-

I have four in a workgroup, rather than on a domain, again behind an ADSL router. Two W98SE, one XP and one Linux. I took the XP machine out of the workgroup and put it on a standalone dialup connection to see if the router was implicated. The problem persisted.

I do not have MS Office installed, I am using OpenOffice. DMON was disabled (in fact deselected during installation of NOD in expert mode) although that does not remove the DMON entry from the control centre, and as we now know, does not entirely disable DMON.

[csmager]

I know the people who've managed to fix this problem are now happy, and the people who don't have the problem were never unhappy in the first place, but I think I've made a discovery.

The last PC, which is in the office, I hadn't bothered checking until today. I tried the pcpitstop test, and it worked (to my disbelief). All PCs are pretty similar in their configurations, seeing as I set all of them up.

I was a little confused as to why this PC should work, so I opened up NOD32 Control Centre and low and behold, DMON was enabled. As it's DMON that appears to cause this problem I was slightly confused. Anyway, all my PCs usually have DMON disabled, and it suddenly struck me that this was the difference in the configs. Maybe we're looking at this the wrong way, I thought.

A bit of a long shot, but I deleted the ActiveX control from C:\WINDOWS\Downloaded Program Files so I could try and download it again... and then I disabled DMON.

Tried the pcpitstop test again, and it failed, just like usual. I then re-enabled DMON, and it was successful.

I'd like anyone who's read this far, if it's not too much trouble, to try this.

E.g. If you've tried the test, and posted 'no problem here' and can't see what the fuss is about, disable DMON, delete mhLabel.class from C:\WINDOWS\Downloaded Program Files and try again. Then re-enable DMON and try a second time.

If you've just used Banicoot's fix, maybe (if you can be bothered, as this one's more time consuming!), install NOD32 from the default installer and try enabling DMON.

If this is the case, then it appears there is a conflict between ActiveX and DMON being disabled, but with it enabled it seems to work fine...

[jmc777]

-{ Quote: "I'd like anyone who's read this far, if it's not too much trouble, to try this.
" }-


Someone buy this gent a drink! :o

I re-installed NOD32, disabled DMON and deleted my flash ActiveX control. Went to the Macromedia website, tried to install the Flash player and it wouldn't install.

Enabled DMON and returned to the Macromedia website, tried to install the Flash player again and.......it installed without a hitch! :D

So the problem only appears when DMON's disabled - this should be easy to fix I'd imagine. Good news!

[Hexaguano]

You are correct csmager!

I reinstalled w/o the "fix". Disabled DMON, and no go. Enabled DMON and the ActiveX control installed/worked fine. Repeated on my other PC. Same result.

[Phil_S]

Same here! Can the people who are seeing this confirm that they are running XP SP2?

When I backed out to SP1 that also resolved the issue. Just tried enabling/disabling DMON on one of the W98 machines, and again that works fine either way.

[Hexaguano]

Yes.

PC #1 - XP Home - SP2 latest "updates".
PC #2 - XP Pro - SP2 latest "updates"

[Bandicoot]

Well done csmager......you're a 'star'! I spent Wenesday afternoon going through 5 user's logs trying to find a common denominator without success. Yesterday was a public holiday in Slovakia, so I was well pleased to see your results today.

I will explain the details of this phenomena to the developers at Eset and hope that they can produce a fix. I'm sure they will be able to.

I will let you all know of developments here on the forum. Thanks again to csmager!

Bandicoot. ;D

[Bandicoot]

Right..... the bug has been fixed and will be issued with the next version of NOD32 which will be version 2.13.0 and should be out fairly soon.... and no, I haven't been told a date yet, sorry...... just very soon.

Bandicoot.
;D

[Phil_S]

Thanks Bandicoot. You're a star ;D

Big thank you to csmager as well ;D

Phil

[Blackspear]

-{ Quote: "Thanks Bandicoot. You're a star ;D" }-Wellll that might be stretching things a little, have you seeeen what a Bandicoot looks like, it's a rodent, some say varmint, though they are tasty when roasted slowly over a spit ;) ;D

;D ;D ;D

[Phil_S]

-{ Quote: "Wellll that might be stretching things a little, have you seeeen what a Bandicoot looks like, it's a rodent, some say varmint, though they are tasty when roasted slowly over a spit ;) " }-

That's as maybe Blackspear, but I think this particular one is much more useful kept alive ;) ;) ;)

[Bandicoot]

What a gentleman and a scholar you are Phil_S! Not like that antipodean bloke, Mr. Spear.

Mr. Coot. ;D ;) :)

[csmager]

-{ Quote: "Right..... the bug has been fixed and will be issued with the next version of NOD32 which will be version 2.13.0 and should be out fairly soon.... and no, I haven't been told a date yet, sorry...... just very soon.

Bandicoot.
;D" }-
Great to hear! Glad it wasn't something unfixable... and I'm really pleased we got to the bottom of it!

Charlie

[Blackspear]

-{ Quote: "What a gentleman and a scholar you are Phil_S! Not like that antipodean bloke, Mr. Spear." }-Damn had to go and look up antipodean, hmmmm quite a pleasant remark for a sanskrit radati ;) ;D ;D ;D


Merriam-Webster Online Dictionary

One entry found for antipode.
Main Entry: an·ti·pode
Pronunciation: 'an-t&-"pOd
Function: noun
Inflected Form(s): plural an·tip·o·des /an-'ti-p&-"dEz/
Etymology: Middle English antipodes, plural, persons dwelling at opposite points on the globe, from Latin, from Greek, from plural of antipod-, antipous with feet opposite, from anti- + pod-, pous foot -- more at FOOT

1 : the parts of the earth diametrically opposite -- usually used in plural; often used of Australia and New Zealand

2 : the exact opposite or contrary
- an·tip·o·de·an /(")an-"ti-p&-'dE-&n/ adjective or noun

Cheers ;D

Mr Spear ;D