If this update fails or is not made, these files can cause the s32evnt1. Thank you very much for posting this information; it enabled me to solve my problem. And I would prefer not editing my Registry with 3yo info. Then have to close. I have renamed s32evnt1. Next, in the left pane of the Registry Editor window, locate the following key: Thank you for helping us maintain CNET’s great community.

Uploader: Migar
Date Added: 25 October 2005
File Size: 32.87 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 8600
Price: Free* [*Free Regsitration Required]

If you use Intel or AMD 64 bit processors, you can download this file: As mentioned before, virtual devices on your system can conflict with Windows and hide the file from being viewed. If this update fails or is not made, these files can cause the s32evnt1.

Failed Virtual Device Driver

Resolution To Fix icfgnt. Can I safely delete these files? We are grateful for any donations, large and small! Before it said value not set.

Remove Norton e.g.

Next, save the file on your hard drive. Flaming or offending other users Illegal activities: See the dll information: However this is not recommended, since it will not remove Ubercode from the list of programs that can be removed by Windows.


Discussions cover Windows Server, Windows dsvice, adding and removing programs, driver problems, crashes, upgrading, and other OS-related questions.

At this point, it is not entirely clear if this corruption is due to a change in the Symantec s32evnt1 dll an installable virtual device as attempts to reproduce this issue have been unsuccessful in a lab environment. You can check everything works properly by building the sample programs. The Symevent files are used by many Symantec products and should be updated regulary. This process ibstallable required by the software to run, so with this error you potentially be s32evnt1 dll an installable virtual device against viruses on your PC.

It seemed to work. How To Fix s32evnt1. Track this discussion and email me when there are updates. This post has been flagged and will be reviewed by our staff.

Y is the version number. Click Start and the Run command.

Error: “S32evnt1.dll. An installable Virtual Device Driver failed DLL initialization”

Yes, it’s a NAV driver that resides here in Registry: It is best that you make a registry back up before editing the registry. Depending on the version of Symantec Antivirus program, perform either of the following: The virtual devices can hide certain files to ensure they run, with s32evnt1.

Click Yes or OK at each prompt. I started having this error after I uninstalled all Symantec products that were on my computer.


Steps to Resolve Initialization Error –

Still hoping that someone will inform us on why we are getting this message and how to correct it. Depending on the type of bit processor you use, download either of the files: If you use Itanium processors, download the Sevinst It must be called somehow in the registry or perhaps Nero or some other apps still think Norton is my antivirus.

If your Symantec antivirus tool is giving you constant problems or you are facing recurring errors related to S3evnt1.dll products, you may wish to opt for equally effective but less error-prone anti-malware software, such as STOPzilla Antivirus and Spyware Cease. Note that in our case no zeros were left as the Symantec article indicated there may be.

I have searched for files that refer to this file and have found none. Update the Symevent files.