Ill tell you something that weird about all this, This issue is not affecting all NOD32 4 systems with SP2. Aparrently some are having Kernel module interface issues when the computer starts- but apparently not many. Eset had difficulty diagnosing the issue, or reproducing the module startup error as a result because of this Irregular/inconsistant occuring error.
When I installed SP2 I didnt disable or remove NOD32 4 from my PC, And I suspect this caused corruption of the app. It is known that NOD32 causes issues with the SP2 installation. I reinstalled the newest build (without manually uninstalling the old one), and I havent had a reoccurance of the disablement issue.
So I just wonder If the manifestation of the error has some sort of trigger. I read one thread, that talked about the OP having difficultly removing the program because of Permissions issues, and had to boot into safe mode to edit the registry. Sounds like Windows/User corruption issues to me. I simply reinstalled the new build over the old one, then ran sfc /scannow-perhaps that made the difference.
In the end, All I know is that I reinstalled the build, and the problem talked about in the Eset kb, and Wilder Forums no longer seems to be an issue for me.
