KB 923980 wants to be installed ever and ever again ?

Discussion in 'Windows Update' started by Crazy-Chris, Nov 15, 2006.

  1. Crazy-Chris

    SquishyBits Guest

    This worked, but the update didn't replace the 'missing' nwapi32.dll
    and when I renamed it back, the update started showing up again. So I
    manually copied over the newer version from the
    $hf_mig$\kb923980\sp2qfe folder and the update is not listed again.
    Should I need to copy/register/do something with the nwwks.dll (and
    nwrdr.sys) file? That's still not showing up in system32, but I get
    the feeling I never needed this whole update to begin with.
    SquishyBits, Nov 26, 2006
    1. Advertisements

  2. Here's what worked for me. Running XP HE SP2 with Spybot resident running.

    In system32, rename nwapi32.dll, nwprovau.dll, nwwks.dll to .OLD if you can.
    (some may return, esp. nwprovau.dll). Erase nwrdr.sys from system32\drivers.

    Uninstall 923980 in ARP.

    Check system32 again, erase any of the 3 files you find there (this was only
    possible for me -after- the uninstall).

    Check system32\drivers to make sure nwrdr.sys did not return (erase if it


    After rebooting and BEFORE updating, find the Spybot resident icon in the
    system tray, right-click on it and select "Exit Spybot-S&D Resident" to turn
    off TeaTimer components (fear not, it will return by itself after the next
    reboot). DO NOT REBOOT NOW.

    Run KB923980 update from the shield in the tray.


    After rebooting, Spybot resident will have returned and the system is now
    The shield has disappeared from the tray and WU no longer reports KB923980
    as being ready to update when I run it from the start menu (in fact, WU shows
    no further updates required at all -- all required patches are currently in

    Further, the 4 files in contention are no longer present in system32 and
    system32\drivers, either.

    Thanks MowGreen for the suggestion that it might be spybot resident that is
    causing the hangup. Temporarily removing it -did- solve the problem.

    Regards to all.

    Just a Cave Dweller, Nov 26, 2006
    1. Advertisements

  3. Crazy-Chris

    engeeaitch Guest

    I have found the same as the post by SquishyBits. However, in my case, having
    removed nwapi32.dll, the automatic update of my Antivirus (CA e-trust)
    stopped working. I manually copied the new nwapi32.dll file across and my
    automatic update started working again, and I am no longer prompted to
    install 923980 (fingers crossed)!

    XP Home, SP2, e-trust Antivirus, Spyware Doctor, Sygate Personal Firewall.
    engeeaitch, Nov 26, 2006
  4. Me thinks, that's an additional issue. There isn't a nwapi32.dll in
    Windows XP Home Edition by default, especially not one with the file
    dates in question ;)

    Ottmar Freudenberger, Nov 27, 2006
  5. It's not ment to do so for Windows XP Home Edition.
    No need to rename it back, if you're not experiencing any problems

    Ottmar Freudenberger, Nov 27, 2006
  6. Now, *that's* indeed interesting (although no one advised yet to
    remove the nwapi32.dll but to rename it. The result "may" be a
    different one)!
    Thanks for sharing,
    Ottmar Freudenberger, Nov 27, 2006
  7. Crazy-Chris

    engeeaitch Guest

    OK - here's my take on what's happening:

    Windows update for 923980 looks to see if nwapi32.dll exists. If it does,
    it checks to see if it is the latest version. If it is not the latest
    version, it prompts to install the update.

    When the update installs, it only updates the nwapi32.dll file if running XP

    As the file does not get updated when running XP Home, when windows update
    next runs, it prompts for 923980 to be installed and the cycle starts all
    over again.

    Normally, nwapi32.dll is not installed in XP Home, so there is no problem.
    However, it can get installed by other programs - in my case e-trust AV.

    And here's the fix:

    Copy nwapi32.dll from C:\WINDOWS\$hf_mig$\KB923980\SP2QFE to
    c:\windows\system32 and re-boot. Job done. (I guess it might be prudent to
    save the original version before overwriting it with the new version).

    P.S. my offending nwapi32.dll was version dated 28 April 1998.
    engeeaitch, Nov 27, 2006
  8. Just found out "other" software may install the NetWare files, Freudi.
    That may be why the update is detected as needed when in fact, it's not
    really needed.
    This appears to be a case of MS attempting to mitigate the vuln just *in
    case* the NetWare service is ever utilized.
    I've not seen any NetWare files on any XP HE OOB

    MowGreen [MVP 2003-2007]
    *-343-* FDNY
    Never Forgotten
    MowGreen [MVP], Nov 27, 2006
  9. Yup, that's what's happening. What's somewhat astonishing is the fact,
    that I've seen some postings now mentioning nwapi32.dll dated
    in 1998. The 1 millon $ question now is, *what* application(s) are
    installing those files and for what purpose.

    Ottmar Freudenberger, Nov 28, 2006
  10. Okay, that's an indication though. You're near the 1 mio $ now ;-)
    Only near, since there are obiviously user out there, which do not
    have e-trust installed but having a nwapi32.dll in Windows XP Home.
    Remarkable, thanks for sharing! :)

    Anyhow, another bad designed update routine,
    Ottmar Freudenberger, Nov 28, 2006
  11. Crazy-Chris

    Bill Y Guest

    I have tried everything detailed in all these posts, and nothing has worked.
    Running XP home, IE7, and norton anti virus and firewall.
    Bill Y, Nov 28, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.