The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    NOT downloading Window's Update KB925902?

    Discussion in 'Windows OS and Software' started by inkyquills, Apr 11, 2007.

  1. inkyquills

    inkyquills Notebook Consultant

    Reputations:
    1
    Messages:
    179
    Likes Received:
    0
    Trophy Points:
    30
    So after reading that thread about how people have been getting relocated DLL registry errors after doing a Windows Update, I've decided not to download the specific Windows Update that causes that problem as someone pointed out in thread.

    Do you guys think it'll be alright not to? I would rather not have to deal with the errors. And before you say you can just download the patch, I don't use Realtek, so that patch doesn't really help at all. When I downloaded the KB925902 update, Window's own calculator program didn't work for me (I would get CALC.EXE -- Relocated DLL registry error). I've since reformatted my computer and updated WITHOUT that update and everything works fine. I'm just wondering how long I would have to hold off before I would have to download it, if ever.
     
  2. mikeymike

    mikeymike Notebook Evangelist

    Reputations:
    70
    Messages:
    696
    Likes Received:
    0
    Trophy Points:
    30
    if u find the update is worse for you

    two words: System restore
     
  3. Pitabred

    Pitabred Linux geek con rat flail!

    Reputations:
    3,300
    Messages:
    7,115
    Likes Received:
    3
    Trophy Points:
    206
    The patch actually DOES help. It's not just for Realtek software, that's just the most common occurrence of the issue. The issue is that an application loads one DLL before another, and Microsoft doesn't deal well with that after the patch (even though it's a perfectly valid thing to do). It's for the general thing that Microsoft screwed up with the initial patch. Go ahead and download both, and you should be fine.
     
  4. zer0pulse

    zer0pulse Notebook Guru

    Reputations:
    0
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    15
    I downloaded the update and thankfully I didn't encountered that error, I also don't use realtek...maybe that's the case? :D