View Full Version : Windows update problem
Jazzer
November 13th, 2005, 01:49 PM
I have evidently deleted something that is preventing the windows update page to come up. I removed norton antivirus because it was causing so much trouble and I also manually removed some symantic files. When I boot my PC it goes to a dark screen and says that I do not have a symevnt.386 file. After pressing a key it finally boots up. When trying to get my windows update it goes to a blank screen. Any suggestions?
DELTREE
November 13th, 2005, 02:44 PM
I hope this is of some help?
>Search for symevnt.386 in the registry and delete the key you find. Should be at:
>
>HKEY_LOCAL_MACHINE\system\current control set\services\vxd
>
>Search for any other instances and delete those as well.
>
>This should fix the problem...Visit www.microsoft.com for info on editing the registry.
Idnew
November 13th, 2005, 03:04 PM
Also delete anything you see as NAV as that is also Norton. Norton has a way of clinging on.
Tom
November 13th, 2005, 06:41 PM
I'd like to suggest a initial first step before Deltree's idea to remove the orphaned registry entry.
1. Click Start, click Run, type sysedit, and then click OK.
2. On the Window menu, click System.ini.
3. On the Search menu, click Find.
4. In the Find box, type symevnt.386, and then press ENTER.
5. Place a semicolon ";" at the beginning of the line that contains "symevnt.386."
6. On the File menu, click Save, and then click Exit on the File menu.
7. Restart your computer.
Then post back if that removed your startup error. At that point you could move to edit out both the system.ini and the registry enries without concern for problems.
DO NOT following any suggestions to haphazardly remove any entries, regardless of their known associations (such as NAV for Norton). Making registry changes without knowing the what function the registry entry serves could lead to rendering your Windows useless, requiring a full reinstallation (and loss of all data).
Jazzer
November 13th, 2005, 09:33 PM
I went through the steps as Jintan directed and when I entered symevnt.386 it could not find it. I looked in the registry as Deltree suggested and found symevnt but it did not have 386 with it. I did a file search and it says that it exist and is in windows/system. I have not made any changes yet.
Tom
November 13th, 2005, 10:11 PM
Jazzer, after running sysedit, in the C:\WINDOWS\SYSTEM.INI window, use the scroll bar to search for that entry. Careful not to make any changes.
Also, do Start-Run, type msconfig. Click on the Startup tab and look for the same entry there. If you do find it, uncheck it, click Apply. Then restart and check to see if it occurs again.
Jazzer
November 14th, 2005, 12:53 AM
This what is on the system.INI window:note: I am running a trial version of AVG, also I looked at the start up menu and did not find anything there.boot]oemfonts.fon=vgaoem.fonshell=Explorer.exesystem.dr v=system.drvdrivers=mmsystem.dll power.drvuser.exe=user.exegdi.exe=gdi.exesound.drv =mmsound.drvdibeng.drv=dibeng.dllcomm.drv=comm.drv mouse.drv=mouse.drvkeyboard.drv=keyboard.drv*Displ ayFallback=0fonts.fon=vgasys.fonfixedfon.fon=vgafi x.fon386Grabber=vgafull.3grdisplay.drv=pnpdrvr.drv SCRNSAVE.EXE=C:\WINDOWS\SYSTEM\3DFLOW~1.SCR[keyboard]keyboard.dll=oemansi.bin=subtype=type=4[boot.description]system.drv=Standard PCkeyboard.typ=Standard 101/102-Key or Microsoft Natural Keyboardmouse.drv=Standard mouseaspect=100,96,96display.drv=SiS 530[386Enh]ebios=*ebioswoafont=dosapp.fonmouse=*vmouse, msmouse.vxddevice=*dynapagedevice=*VCDdevice=*vpdd evice=*int13device=*enablekeyboard=*vkddisplay=*vd d,*vflatdEMMExclude=C000-CFFF[NonWindowsApp]TTInitialSizes=4 5 6 7 8 9 10 11 12 13 14 15 16 18 20 22[power.drv][drivers]wavemapper=*.drvMSACM.imaadpcm=*.acmMSACM.msadpcm= *.acmwave=mmsystem.dllmidi=mmsystem.dll[iccvid.drv][mciseq.drv][mci]cdaudio=mcicda.drvsequencer=mciseq.drvwaveaudio=mc iwave.drvavivideo=mciavi.drvvideodisc=mcipionr.drv vcr=mcivisca.drvMPEGVideo=mciqtz.drvMPEGVideo2=mci qtz.drv[vcache][Password Lists]DEFAULT=C:\WINDOWS\DEFAULT.PWLHP AUTHORIZED CUSTOM=C:\WINDOWS\Hpauthor.pwlSTUART GREEN=C:\WINDOWS\STUARTGR.PWL[MSNP32]0 22=13 22[network]NIC=29395997
Jazzer
November 14th, 2005, 12:56 AM
Let me try to post that again and see if it is better, It isn't all run together like that:boot]oemfonts.fon=vgaoem.fonshell=Explorer.exesystem.dr v=system.drvdrivers=mmsystem.dll power.drvuser.exe=user.exegdi.exe=gdi.exesound.drv =mmsound.drvdibeng.drv=dibeng.dllcomm.drv=comm.drv mouse.drv=mouse.drvkeyboard.drv=keyboard.drv*Displ ayFallback=0fonts.fon=vgasys.fonfixedfon.fon=vgafi x.fon386Grabber=vgafull.3grdisplay.drv=pnpdrvr.drv SCRNSAVE.EXE=C:\WINDOWS\SYSTEM\3DFLOW~1.SCR[keyboard]keyboard.dll=oemansi.bin=subtype=type=4[boot.description]system.drv=Standard PCkeyboard.typ=Standard 101/102-Key or Microsoft Natural Keyboardmouse.drv=Standard mouseaspect=100,96,96display.drv=SiS 530[386Enh]ebios=*ebioswoafont=dosapp.fonmouse=*vmouse, msmouse.vxddevice=*dynapagedevice=*VCDdevice=*vpdd evice=*int13device=*enablekeyboard=*vkddisplay=*vd d,*vflatdEMMExclude=C000-CFFF[NonWindowsApp]TTInitialSizes=4 5 6 7 8 9 10 11 12 13 14 15 16 18 20 22[power.drv][drivers]wavemapper=*.drvMSACM.imaadpcm=*.acmMSACM.msadpcm= *.acmwave=mmsystem.dllmidi=mmsystem.dll[iccvid.drv][mciseq.drv][mci]cdaudio=mcicda.drvsequencer=mciseq.drvwaveaudio=mc iwave.drvavivideo=mciavi.drvvideodisc=mcipionr.drv vcr=mcivisca.drvMPEGVideo=mciqtz.drvMPEGVideo2=mci qtz.drv[vcache][Password Lists]DEFAULT=C:\WINDOWS\DEFAULT.PWLHP AUTHORIZED CUSTOM=C:\WINDOWS\Hpauthor.pwlSTUART GREEN=C:\WINDOWS\STUARTGR.PWL[MSNP32]0 22=13 22[network]NIC=29395997
Tom
November 14th, 2005, 01:56 AM
That all looks fine. How about the msconfig?
Jazzer
November 14th, 2005, 03:00 AM
The start up menu does not show any symevnt.386 or any other symantec processes running.
Tom
November 14th, 2005, 03:18 AM
Those were the easy way. Now it's time to roll up your sleeves. I have seen many problems coming out of incomplete removal of Norton. In this case you would be most able to I.D. what parts you might have missed. I would suggest reviewing These (http://service1.symantec.com/SUPPORT/nav.nsf/docid/2001092114452606) manual removal manuals and see where you might add the missing step to resolve the current issues. I woldn't recommend doing any guesswork on it - Norton when installed has a hand in just about every part of system operations. Incorrect removal = problems.