1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows doesn't boot after critical update: "unknown error (code 5)"

Discussion in 'Legacy Windows' started by jonathang, 2004/08/21.

Thread Status:
Not open for further replies.
  1. 2004/08/21
    jonathang

    jonathang Inactive Thread Starter

    Joined:
    2004/08/21
    Messages:
    2
    Likes Received:
    0
    I've had a Gateway PC since 2000 - Windows 98 SE. Only problem has been that it sometimes gets errors on reboot which seem to be realted to McAfee VirusScan - but when I continue, reboot completes OK.

    Today I tried to add some critical updates from the Micorsoft update page - seemed to go OK until I got to rebooting the PC. Boot seems to go Ok - gets to the "Windows 98" banner screen, but then just stays there - I've tried leaving the PC for several hours but no further progress, it just stays on that screen. The only thing that has any effect is to press ESC - then the Windows banner disappears, and the DOS boot appears - with the message:

    128 ... unknown error (code 5)

    After this the only possible thing to do is Cntrl-Alt-Del, or to power off - both of which just start again. Any ideas how to solve this? I can't remember how to get into Windows safe mode - and not sure what I would do if I could.

    Background: Win 98 SE which is reasonably up-to-date with fixes etc from Microsoft - about 4 critical updates loaded today, these were the only ones due. McAfee VirusScan v4.1.60. Netgear wireless card, has worked fine in the past.

    Thanks for any help
    Jonathan
     
  2. 2004/08/22
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400

  3. to hide this advert.

  4. 2004/08/22
    jonathang

    jonathang Inactive Thread Starter

    Joined:
    2004/08/21
    Messages:
    2
    Likes Received:
    0
    Thanks for information - I had searched but hadn;t found it. Seems to be a problem with McAfee v4.1.60 - pity McAfee don't warn about this...
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.