0x8ddd0007 error

  • Thread starter Thread starter skeetz
  • Start date Start date
S

skeetz

Guest
Im running win xp home sp2...I just did a repair and when I booted back up I
got the windows update box that said it was going to install windows
installer 3.1....when it was done it said I had to reboot...which I did...and
now it wont go away....I've also run sfc /scannow


When accessing the Update site, you receive the 0x8ddd0007 error

Click Start. Choose Run. In the Open box, type regedit. Click OK.
I
n the Registry Editor, go to the following branch:

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

If the RebootRequired sub-key is present, right click on the key and then
click on the Delete option. Click Yes for confirmation.

I've done this 100 times, I have run Adaware, Spybot, AVG and Panda scans
found nothing. I had a Microsoft tech check for corrupted windows and
registry folders...nothing...so the tech told me that the version of
installer I have on my pc now is probably corrupted and I would need to do
another repair to fix it....so I did that and it still didn't fix it....the
version of installer per the dll is this

C:\WINDOWS\system32 Windows Installer 3.0.3790.2180



It doesnt matter what I try I keep getting the icon in my taskbar
....updating your computer is almost complete..restart for updates to take
effect....every 10 mins it pops up to remind me...never ends....if anyone can
suggest something else for me to try I would greatly appreciate it.
 
I just tried deleting the
RebootRequired sub-key again and was able to access win update and now got
this new error message but it wont let me install the fix for it....


Error message when you try to update a Microsoft Windows-based computer:
"0x80070002"



Update for Windows XP (KB922582)
Date last published: 9/12/2006
A problem has been identified in Filter Manager that can prevent you from
installing
updates from Windows update. You can help protect your computer by
installing this
update from Microsoft. After you install this item, you may have to restart
your computer.
System Requirements
Recommended CPU: Not specified.
Recommended memory: Not specified.
Recommended hard disk space: Not specified.
How to Uninstall
This software update can be removed via Add or Remove Programs in Control
Panel.
Get help and support
http://support.microsoft.com
More information

http://support.microsoft.com/kb/922582

any ideas how I can get this installed or get the filters off that are
blocking me ?










"skeetz" wrote:

> Im running win xp home sp2...I just did a repair and when I booted back up I
> got the windows update box that said it was going to install windows
> installer 3.1....when it was done it said I had to reboot...which I did...and
> now it wont go away....I've also run sfc /scannow
>
>
> When accessing the Update site, you receive the 0x8ddd0007 error
>
> Click Start. Choose Run. In the Open box, type regedit. Click OK.
> I
> n the Registry Editor, go to the following branch:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
>
> If the RebootRequired sub-key is present, right click on the key and then
> click on the Delete option. Click Yes for confirmation.
>
> I've done this 100 times, I have run Adaware, Spybot, AVG and Panda scans
> found nothing. I had a Microsoft tech check for corrupted windows and
> registry folders...nothing...so the tech told me that the version of
> installer I have on my pc now is probably corrupted and I would need to do
> another repair to fix it....so I did that and it still didn't fix it....the
> version of installer per the dll is this
>
> C:\WINDOWS\system32 Windows Installer 3.0.3790.2180
>
>
>
> It doesnt matter what I try I keep getting the icon in my taskbar
> ...updating your computer is almost complete..restart for updates to take
> effect....every 10 mins it pops up to remind me...never ends....if anyone can
> suggest something else for me to try I would greatly appreciate it.
>
>
>
 
"skeetz" wrote:

> Im running win xp home sp2...I just did a repair and when I booted back up I
> got the windows update box that said it was going to install windows
> installer 3.1....when it was done it said I had to reboot...which I did...and
> now it wont go away....I've also run sfc /scannow
>
>
> When accessing the Update site, you receive the 0x8ddd0007 error
>
> Click Start. Choose Run. In the Open box, type regedit. Click OK.
> I
> n the Registry Editor, go to the following branch:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
>
> If the RebootRequired sub-key is present, right click on the key and then
> click on the Delete option. Click Yes for confirmation.
>
> I've done this 100 times, I have run Adaware, Spybot, AVG and Panda scans
> found nothing. I had a Microsoft tech check for corrupted windows and
> registry folders...nothing...so the tech told me that the version of
> installer I have on my pc now is probably corrupted and I would need to do
> another repair to fix it....so I did that and it still didn't fix it....the
> version of installer per the dll is this
>
> C:\WINDOWS\system32 Windows Installer 3.0.3790.2180
>
>
>
> It doesnt matter what I try I keep getting the icon in my taskbar
> ...updating your computer is almost complete..restart for updates to take
> effect....every 10 mins it pops up to remind me...never ends....if anyone can
> suggest something else for me to try I would greatly appreciate it.
>
>
>
 
"skeetz" <skeetz@discussions.microsoft.com> wrote in message
news:6D7AD6E8-58EA-4DFD-BBB9-0FEC0F84C4B6@microsoft.com...
> Im running win xp home sp2...I just did a repair and when I booted back up I
> got the windows update box that said it was going to install windows
> installer 3.1....when it was done it said I had to reboot...which I did...and
> now it wont go away....I've also run sfc /scannow



When it asks you to reboot it means that there is a list of modules in a registry
value called PendingFileRenameOperations which were in use when the update
was run. Usually a "pending file rename operation" is a temporary name
which is to replace an existing name. You can open that value name and
capture its contents. Then you can check the versions of the modules involved.
Check the same modules after the boot. The value contents do not survive the boot.

If the modules are not being copied or renamed that would explain your symptom.
A possible cause of such a problem would be an overzealous security program.
E.g. it might think it was detecting (and successfully blocking) a Trojan trying to install itself.
Do you have such a security program active during your reboot? Does it provide
a log of its activities? Look for clues there or ensure that it is disabled before
retrying the update (or any update which requires a reboot.)

You may also be able to detect more details about the names of the modules
in use and the programs which are using them by looking for entries in the Event
Viewer's Application log. Who knows, maybe the (hypothetical) security program
logs in there too and nobody has noticed so far? Be a trailblazer? ; )


Good luck

Robert Aldwinckle
---
 
Back
Top