Link to home
Start Free TrialLog in
Avatar of Juan Velasquez
Juan VelasquezFlag for United States of America

asked on

16 Bit Windows Subsystem Error Message

Hello,

I've removed symantec from my PC which is running Windows XP Professional.a while ago  Since then I have been getting the the following message box upon bootup

C:\PROGRA~1\Symantec\S32EVNT.DLL. An installable Virtual Device Driver failed Dll initialization.  Choose 'Close' to terminate the application.  The title of the message box is 16 Bit Windows Subsystem.  If I choose Close, the system reboots.  How do I get rid of this error message.  I thought I had completely removed the Symantec application
Avatar of jasondavidcarr
jasondavidcarr
Flag of United States of America image

Search the Windows registry for S32EVNT.DLL and remove all references.  Make sure you back up the registry, first, though, in case something gets messed up.

To edit the registry, go to Start, Run, and type "regedit".  Hit OK and it will bring up the registry editor.

Back up the registry first, run a search for S32EVNT.DLL, and then delete out all references you find.
Avatar of Juan Velasquez

ASKER

I ran a search for all references for S32EVNT.Dll and there were zero search results.
ASKER CERTIFIED SOLUTION
Avatar of jasondavidcarr
jasondavidcarr
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I went ahead and purchased emeditor and am executing the search.
I tried executing the search and Microsoft generated an error report message
Never mind I think I found the reason that I received the error message.  I'm trying the search again
Hi,

I've completed the search and have the results.  There are many log files that are referencing S32EVNT1.DLL
I have found the problem.  I deleted the "C:\Program Files\Symantec Shared" folder, deleted the Symantec Live update program and then modified the registry as per
http://support.microsoft.com/kb/314452/ by deleting the VDD in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD which had been apparently corrupted and then recreating it

Glad to hear you found a solution. :)
The primary error was a corrupted registry error as I describes.  However, the proffered solution was extremely helpfull in narrowing the problem