We need to pay particular attention to the instructions as they say to delete the data for the indicated key, not delete the key itself!We navigated to the required registry location: and SBS... Followed by choices "Close" or "Ignore". An installable Virtual Device Driver failed DLL initialization” error on a 32-bit and 64-bit Windows XP computer. weblink
All rights reserved. An installable Virtual Device Driver failed DLL initialization" occurs during LiveState Delivery image capture Was this article helpful? Java Internal Error 2755. 1624, ...jre1.6.0_07-ift... Insane Storage Volume - 1.5TB Drives hitting the s... https://support.symantec.com/en_US/article.TECH100470.html
S32EVNT1.dll « Reply #1 on: July 13, 2006, 10:52:34 PM » Yes, it's a NAV driver that resides here in Registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\\VDDHKEY_LOCAL_MACHINE\SYSTEM\ControlSet... 3 numbers ...\Control\VirtualDeviceDrivers\\VDDAbout aswMonVd.dll and s32evnt1.dll in registry keys, see It seemed to work. SBS 2008 Canuck Launch - Input needed Caseware Working Papers 2008 - Data Store Error 0x... This will allow you to restore the registry in case any complications occur.
Click I accept the License Agreement, and click Next. Create a SymAccount now!' Support / Error: "S32evnt1.dll. Click Run. In the Data Type drop-down menu, click REG_MULTI_SZ, and then click OK.
dlrjmr2 Visitor2 Reg: 27-May-2013 Posts: 1 Solutions: 0 Kudos: 0 Kudos0 Annoying pop-up notice about "16 Bit Windows Sub-System", reading "C:\Program\Symantec\S32EVNT1.DLL" Posted: 27-May-2013 | 2:24PM • 3 Replies • Permalink Notice Next, save the file on your hard drive. Next, open the Command Prompt window by running the CMD command at Start > Run. No Yes Products Products Home Services Services Home Solutions Solutions Home Support Center Security Center Security Center Home Partner United States / English Sign In/Register Hi My Account Log out Search
Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Any advice on how to eliminate the pointer to this Norton reminant? forums with the same problem: http://forum.avast.com/index.php?topic=707.msg3417#msg3417How to remove NAV and be happy 1) Remove NAV through Add/Remove programs from Control Panel. Restart your PC.
In the left pane, right-click the VirtualDeviceDrivers key, select New, and then select Multi-String Value. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. An Installable Virtual Device Driver Failed Dll Initialization Windows 7 Download and save these three files to the Windows desktop: a) ftp://ftp.symantec.com/public/english_us_canada/linked_files/tsgen/MSIFIX.bat b) ftp://ftp.symantec.com/public/english_us_canada/linked_files/tsgen/SymNRT.exe c) ftp://ftp.symantec.com/public/english_us_canada/linked_files/tsgen/SYMMSICLEANUP.reg2. Symevent Follow the above steps to successfully resolve “S32evnt1.dll.
To update the Symevent files Follow the directions in the document Updating the Symevent files. have a peek at these guys So, after double clicking on the shortcut, that is the error that we received.To date, we have never seen this one!A quick search turned up a couple of Symantec technical articles:Errors Can I safely delete these files? On the Edit menu, click Add Value.
Proffitt Forum moderator / September 25, 2008 3:29 AM PDT In reply to: Windows XP: error message While it's nice to see you offer a solution, after 3 years they likely Don't have a SymAccount? Flag Permalink This was helpful (0) Collapse - Watch those post dates by traveling_engineer / July 23, 2009 10:52 AM PDT In reply to: Watch those post dates. check over here While it's true that the original poster has probably long since moved on, with the magic of Google, other people can find this thread when they're having the same problem, and
I'm a bit new to registry editing, so I wasn't sure exactly what to do. Running Windows XP. I'm a Microsoft MVP since 2009.
Technical Information For more information about this problem, read the Microsoft Knowledge Base document Virtual Device Driver Error Message in 16-Bit MS-DOS Subsystem (254914). Sorry, there was a problem flagging this post. Depending on the version of Symantec Antivirus program, perform either of the following: If you use Symantec Antivirus 9.x or later, type either of the following command, depending on the file Thank you for your feedback!
Thank you for helping us maintain CNET's great community. I started having this error after I uninstalled all Symantec products that were on my computer. Logged Lisandro Avast team Certainly Bot Posts: 67089 Re: Remove Norton e.g. this content The program receives regular updates for Canadian tax updates and the like.
Thank you for your feedback! Solution Edit the regitry to change how the VirtualDeviceDrivers key works. Flag Permalink This was helpful (0) Back to Windows Legacy OS forum 15 total posts Popular Forums icon Computer Help 51,912 discussions icon Computer Newbies 10,498 discussions icon Laptops 20,411 discussions Try these resources.
Run the three files that you just downloaded a) On the Windows desktop, double-click the MSIFIX icon. Print Article Subscribe to this Article Manage your Subscriptions Create Case Search Again Situation When booting the machine, or when launching a 16-bit application like command.com, you get the following error: Choose 'Close' to terminate the application.-or-16 bit MS-DOS Subsystemdrive:\program pathSYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. Next, in the left pane of the Registry Editor window, locate the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers Next, in the right pane, locate and delete the VDD value.
In the Run dialog box, type regedit Click OK. That's what I did, and I was very glad that it helped me solve my problem! Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. Only proceed if you are comfortable in editing the registry.
The original poster had:C/progra~1\symantec\s32evnt1.dllyours probable is:c:\progra~1\symantec\s32evnt1.dllAnyway, try the following procedure :Errors regarding 16-bit MS-DOS subsystem from Symantec's site.Good Luck,CetinTrying to unweave, unwind, unravelAnd piece together the past and the future,T. Then update the Symevent files and restart the computer again.