WU Active X: This is normal?

Discussion in 'other security issues & news' started by Untouchable J, Oct 4, 2005.

Thread Status:
Not open for further replies.
  1. Untouchable J

    Untouchable J Registered Member

    Joined:
    Jul 5, 2004
    Posts:
    53
    My cuzin computer had a bunch of crap installed, so I decided to reformat for him. After installing my drivers, and SP2, I went on Windows update(V6) to download the latest patches for his computer.

    I get the standard prompt to download and install the standard wuweb.dll active X control, but after I click install I get the slide down prompt in IE saying it prevented the site from installing an Active X control. I choose to allow the active x control (refresh the site), then I get the prompt saying IE blocked ocget.dll because it cant verify the file. o_O

    I didnt have these prompts when using V5, so I wanted to know is other people getting these prompts also and its legit or its something I should dig deeper with.

    Thanks

    -J
     
  2. Tom772

    Tom772 Guest

    Hi, I recently asked the same question as there are two Active X updates for Windows Update and Microsoft Windows Update > both are safe. There is a link in this thread that should help, Tom

    https://www.wilderssecurity.com/showthread.php?t=97393&highlight=Microsoft update
     
  3. Tom772

    Tom772 Guest

    (I choose to allow the active x control (refresh the site), then I get the prompt saying IE blocked ocget.dll because it cant verify the file). Hi again! in regards to the DLL being blocked or because it could not verify it, there is this link that should help

    http://www.securityfocus.com/archive/1/315165/2003-03-11/2003-03-17/0

    regards T:)
     
  4. Rico

    Rico Registered Member

    Joined:
    Aug 19, 2004
    Posts:
    1,703
    Location:
    Texas
  5. Untouchable J

    Untouchable J Registered Member

    Joined:
    Jul 5, 2004
    Posts:
    53
    Thats for the info....

    Should of ran a quick google search b4 posting this thread, I would of found MS's workaround.

    -J
     
Loading...
Thread Status:
Not open for further replies.