[Error number: 0x8DDD0007]

Discussion in 'Windows Update' started by Steve, Aug 25, 2004.

  1. Steve

    Steve Guest

    Hey,

    I reported the following error in a post to this newsgroup several days ago,
    with no response.

    [Error number: 0x8DDD0007]
    Windows Update cannot be displayed because your computer requires
    you to restart it in order to finish another process. For example, you may
    have installed a program or update recently. After restarting, click Start,
    and then click Windows Update.

    I did try rebooting several times, but there was no getting rid of that
    error.

    Now, there was no response to my post, I assumed, because my problem may
    have been unusual or unsolvable. My problem began when I encountered (and
    accepted with a 'yes') the following prompt while running Windows Update on
    my machine:

    "Do you want to install and run "Windows Update" signed on 8/3/2004 6:47PM
    and distributed by: Microsoft Windows Publisher? Publisher authenticity
    verified by Microsoft Windows Verification Intermediate PCA."

    So I did a system restore previous to this install, and hey wow, no more
    error number 0X8DDD0007. Now I'm back to the same request to install
    Windows Update of course, which I am currently refusing.

    Does anyone have any advice at this point? Is this something I can adjust,
    or is there a bug fix that might be coming?

    Sure would appreciate any help,

    Steve
     
    Steve, Aug 25, 2004
    #1
    1. Advertisements

  2. Steve

    Dave Guest

    I have similar error (0x8DDD0018). Nothing on the MS site
    and so I am about to check www.annoyances.org to see if I
    can find anything.

    May be worth a look.

    Good luck
     
    Dave, Aug 25, 2004
    #2
    1. Advertisements

  3. Steve

    J_Nitzberg Guest

    I am using an Acer C110 Tablet PC. Before I decided to go to SP2 via
    the SP2 for IT Professionals Download, I had been getting at the
    version 5 Windows Updates site, the 0x8DDD0007 error. From searching
    around, I found that what is installed is a DLL file called
    "wuweb.dll" dated 8/5 or 8/3 I think. If you run the command "regsvr32
    /u wuweb.dll", it will un-register the DLL, and if you reboot, you can
    then delete it. Then, if you go to v5.windowsupdate, it will
    re-download the software from Microsoft. BUT, the same error would
    happen to me. I tried going to v4.WindowsUpdate, but be automatically
    redirected to v5. I found a work around to this by going to the v4
    catalog page at: http://v4.windowsupdate.microsoft.com/catalog/en/default.asp
    , then click on the link in the lower left to go to Windows Update ver
    4. It may ask you to 'update your active x control', and it scanned my
    system, but I have yet for it to find any critical updates, so I am
    not sure if this actually works.

    Now, I installed SP2 last night (with a clean startup through
    msconfig). After finding the Norton WMI patch to fix my
    SystemWork/Antivirus'03, the status in the Windows Security Center has
    a green/good to go (at
    http://www.neowin.net/comments.php?action=crf&category=software&cid=266992&id=23322
    ) . BUT, everytime I reboot, the yellow pennant is at the bottom of
    the screen saying "Automatic Updates: Updating your computer is almost
    complete. You must restart your computer for the updates to take
    effect" and no matter how many times I hit 'restart now', it still
    comes up. Extremely annoying!! Even if I turn off AU, the yellow
    warning still comes up.

    I was hoping SP2 would fix the 0xDDD0007 error, but it didn't. I think
    these two issues are related, but not sure by what. Another gentlemen
    said to look at your windowsupdate.log file, but it doesn't seem to
    give any indication of problem.
     
    J_Nitzberg, Aug 27, 2004
    #3
  4. Steve

    J_Nitzberg Guest

    Thanks to a gentleman by the name of Igor Franchuk, he has found the
    fix to this problem, and it so easy, it makes me mad.

    Here is what we sent to me:

    " I've encountered the same problem as you did today. When searching
    the
    Internet for the same error in hope for a ready solution in
    some discussion forum I surfed over quite a few responses and none
    of them were solutions.

    After giving up I came up with a solution of our problem. It seems
    like there was actually a mistake in the previous versions of
    windows update.

    After disassembling wuweb.dll that is responsible for webControl
    update ActiveX object that is actually handling web based updates
    I discovered the place where reboot required message is generated.
    After looking in around the code I found that the condition
    the message is generated is the presence or absence of

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired

    key.

    If the key exists - the message is generated by that brand new v5
    update and it fails to work further causing [Error number:
    0x8DDD0007].

    I assume this key was set up in my registry long ago by the when the
    old automatic
    update (taskbar version) was uploading a new software and failing to
    install it.

    The solution then is simple remove the key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired

    so there would be only

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update

    key without RebootRequired entry.

    REGEDIT4
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired]


    After I removed the key RebootRequired v5 update started to work
    happily, and installed a new version of wuauclt.exe
    "

    It worked for me wonderfully, and I feel a lot better about sp2. Hope
    this helps those in need!
     
    J_Nitzberg, Aug 31, 2004
    #4
  5. Steve

    J_Nitzberg Guest

    Ladies and Gentlemen, and jurors of the court, I think we have a
    ruling ...

    and Mr. Igor Franchuk is the winner (or at least one of the first that
    I have been able to see/find to fix error 0x8DDD0007 )

    This is what he sent me:

    " I've encountered the same problem as you did today. When searching
    the
    Internet for the same error in hope for a ready solution in
    some discussion forum I surfed over quite a few responses and none
    of them were solutions.

    After giving up I came up with a solution of our problem. It seems
    like there was actually a mistake in the previous versions of
    windows update.

    After disassembling wuweb.dll that is responsible for webControl
    update ActiveX object that is actually handling web based updates
    I discovered the place where reboot required message is generated.
    After looking in around the code I found that the condition
    the message is generated is the presence or absence of

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired

    key.

    If the key exists - the message is generated by that brand new v5
    update and it fails to work further causing [Error number:
    0x8DDD0007].

    I assume this key was set up in my registry long ago by the when the
    old automatic
    update (taskbar version) was uploading a new software and failing to
    install it.

    The solution then is simple remove the key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired

    so there would be only

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update

    key without RebootRequired entry.

    REGEDIT4
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\RebootRequired]

    After I removed the key RebootRequired v5 update started to work
    happily, and installed a new version of wuauclt.exe"


    It fixed my tablet! Also, I found out that the splash screen changed
    to just Windows XP (no pro, no home, no tablet, just XP) and this is
    by design for SP2...I dont like it, but that is completely un-related
    to the 0x error.
     
    J_Nitzberg, Sep 3, 2004
    #5
    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.