MS Updates "Error 0x8DDD0007" (Re-Booting)

Hello, Everybody !

PLEASE help me KILL Windows Updates "Error 0x8DDD0007" !!!

Following a "Repair-Reinstall" of the Windows XP (Home) SP1 OS on my Dell Dimension 8300 Desktop computer last Tuesday (3-03-2008) morning, I installed WinXP SP2 and went to Microsoft Updates to download and install the dozens of updates that I knew would be needed.

Unfortunately, I was unable to access the MS Updates page and encountered "Error 0x8DDD0007 ".

The text of "Error 0x8DDD0007" reads : "You need to restart your computer to finish installing a program or updates. You cannot view or get other updates from the site until you restart."

So I re-booted the computer, got back online, and went back to the MS Updates page only to encounter "Error 0x8DDD0007 ". Thinking maybe I'd done something wrong (Hey, it's been known to happen...), I once again went throught the re-boot process and once again ran into "Error 0x8DDD0007 ".

I've owned this computer since July, 2003 (NEW) and I've done two or three Repair-Reinstalls, the last one being in March, 2007. I've never encountered "Error 0x8DDD0007" until last Tuesday. Since then, I've had to do FOUR (or was it five?) of them.

Before I go any farther into this post, let me say that for the past six days I've spent 15-20 hours per day searching, researching, and trying ALL of the "solutions" (and variations of them) to this (and others related to) "Error 0x8DDD0007" problem. Of the 6,000+ pages listed in a Google search, I've visited the first 500 or so. Dozens of websites and pages, and hundreds of entries. But to no avail.

One of the most common "solutions" referenced to "Error 0x8DDD0007 ", dates back (I believe) to January, 2004. It is a fairly easy registry "hack ". Using the "RegEdit" (Registry Editor) you go find the following HKey Local Machine key :

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AutoUpdate\RebootRequired\Mandatory.

The idea of the "hack" is to delete the "Mandatory" and/or "Reboot Required" key(s), and then re-boot your computer. Without the "demand" of a required reboot, MS Updates will let you in and you can the go through the "normal" updating process.

Now, that might have worked for some folks back in 2004 and 2005, but has NOT worked for me in March, 2008!

That registry key (RebootRequired\Mandatory) constantly, consistently, and repeatedly keeps RE-APPEARING (ad nauseum) and DEMANDING that I keep re-booting my machine !!!

It's like the "Mother-of-all-CATCH-22's-of-MS-Updates" !!!

I want to KILL whatever it is that causes "Error 0x8DDD0007 ", and I NEED your help to do it.

I need to know what part of Windows XP (Home) keeps re-generating that registry key (RebootRequired\Mandatory), where it's located, and how to get rid of (KILL) it.

Won't you help me (and untold others) get rid of this problem ???

For those of you who are willing to help and have an idea that you think might work, please remember that I've spent the better part of the past six days scouring the internet and dozens of websites for "the answer ". I've tried a LOT of different things (NONE of which worked), but I honestly doubt that I've tried "everything ".

For those of you that want to suggest that I go to Microsoft.Com and try their "solutions ", I want you to know that I've been there (many times), done that (many times), and it didn't work (not even once).

For those of you who would like to suggest that maybe I need to "register" some updates-related DLL files, I assure you that I've tried every single combination of those that I've found. I've registered, un-registered, re-registered any number of combinations of DLL's, in various steps in both regular and "safe" modes of operations. None of them worked.

If you think that all that needs to be done is to update MS's "Windows Installer ", you might be right. I currently have version 3.0 installed on my computer, and the newest version is 3.1. And THAT might very well be the "source" of the problem, or at least partially so. I have the installer package for MS's "Windows Installer" version 3.1 sitting on my desktop. Unfortunately, I can't install it because it won't do so until after I complete the required MANDATORY re-boot. Which, of course, does absolutely no good, whatsoever!

How about the Windows "Update Agent "? I actually managed to download AND install it on my computer! It didn't do any good, mind you, but at least I got it installed!

Maybe ".NET Framework" packages? I don't know if any of them would have a bearing on this problem or not. since I already had all of the .NET Framework installation packes on my computer I started installing them. I only got as far as installing .Net Framework 2.0 before the DEMAND for the MANDATORY re-boot popped up. Nothing later than that (v.2.0) would install.

Ah.... right about now some of you might be thinking that maybe some little malware creature weaseled its way onto my machine and is preventing all of the MS updates from downloading. Hmmm... I don't think so. I've ran most of my Anti Spy/Malware and antivirus products in both regular and "safe" mode, including a couple of "rootkit" apps. Nothing was found.

Anti-Virus, Anti-Spyware, or firewall blocking access to the updates? Maybe... but I don't think so. I've tried various schemes with some/all of them disabled. I even completely un-installed and re-install McAfee's Security Center TWICE! I'm using the Windows XP firewall and it only blocks INBOUND traffic, not outbound, so I don't think that's it either.

I even went so far as to turn off Windows Update (in the Control Panel), used the Services.msc application to completely disable and stop the Automatic Updates service and the BITS (Background Intelligent Transfer Service) on my machine and went to MS Updates! And what did I find there?

"Error 0x8DDD0007" !!!

But then, in a stroke of inspired desperation, I opened up RegEdit and deleted the "RebootRequired\Mandatory" registry key, and "refreshed" the MS Updates page and what did I get ???

I got IN !!!

There were only FIVE updates listed for my machine. The last time I did a Repair-Reinstall in March of 2007, there were 45. I figured there would be at least 70-80 updates to install. Oh, well. I'll take what I can get, or at least four out of the five (I don't need or use MS's Virtual Java Machine).

I was able to download all four updates selected and then.....

I was unable to install them. Apparently, I needed to do the now-required MANDATORY RE-BOOT !!!

And so it went, and so it's gone, and so it goes.....

SIGH . . . . .

Some of you folks might have the same idea I had: Why not bypass the MS/Windows Updates thing altogether?

Instead of trying to access the Updates web-page to download God-knows-how-many updates, why not download and install Windows XP Service Pack 3 Release Candidate 2 ??? GREAT idea, right ???

Except that I already had SP3/RC2 downloaded and on my computer. When I tried to install it, I got the same exasperating "MANDATORY Re-Boot Required" message as all those many, many times before.

All in all, I think that there are only about 7-10 proposed "solutions" for "Error 0x8DDD0007" and the incessant and repeated calls to re-boot the computer. Unfortunately for me (so far) the many dozens of "solutions" that I've found are merely "Copy/Paste" entries referencing to those 7-10 "proposed" solutions.

I honestly doubt that ANY of the so-called "experts" who have offered any kind of "solution" to correct/fix "Error 0x8DDD0007 ", have actually did a Repair-Reinstall to see if their solution would actually work in the "real" world.

But, anyway.....

Thank You for taking the time to read all of this. I appreciate it, I really I do!

So, there you have it.

Can YOU help me KILL "Error 0x8DDD0007" ???

I (and my computer) sincerely hope so !!!

FOR THE RECORD :

DELL Dimension 8300 Desktop
Windows XP (Home)
Repair-Reinstall with Computer's WinXP SP1 Disk
WinXP SP2 installed
IE 6 Browser

As it now stands...

Can NOT access MS/Windows Updates.
BelArc Adviser shows 97 Critical updates missing.
Constant mandatory re-boot requests.
WinXP SP3/RC2 will NOT install.
.NET Framework 2.0 SP1 and later will NOT install.
IE7 will NOT install.
Windows Installer 3.1 will NOT install.
Windows update Agent INSTALLED.
Windows Clock will NOT adjust for Daylight Savings Time.
OTHER Windows related/connected will NOT install w/o "Re-Boot ".

You've all been very patient with me and I Thank You for that.

ROBIN
Eugene, Oregon USA

 

Pete sorry to bud in, but isn't there a patch available at MS as this is a common problem after a Repair install, I did try to find it but can't at the moment.

 

http://support.microsoft.com/kb/555615/en-us

That is what I was looking for I don't know if a solution is there or not but worth looking at

 

Thank You For Replying... But Wait! There's MORE !!!

Thank You, Pete !
Thank You, Hawk !
Thank You, Arie !

Thank You for your replies! Unfortunately, things haven't quite worked out as well as we might have wanted them to. Since I'm not quite sure where to begin, or how to organize my response(s), I guess I'll just start at the beginning and kind of bumble, stumble, and waltz my way through!


PeteC !

My post wasn't really all that clear and concise, but it was a LOT more concise (I hope) when I edited out about 60-70% of the original!

During one of my Repair-Reinstall attempts (the 3rd one, I think), I did happen to have to uninstall & reinstall SP2. There was NO improvement. I have both the copy of SP2 on CD that I got from MS when it first came out, and I have a copy of it that I downloaded from MS a few months ago. I used the DL'ed copy for the first R-R's and then the CD copy on this latest one. [BTW: the DL'ed SP2 takes about 15 minutes to install and the CD about 25.]

As far as your suggestion to do a "Clean Install of XP ", I can think of two reasons why that probably won't work.
#1) I don't have the means to do a clean install. Meaning, I don't have a way to transfer all of the non-MS data off my computer (Which would be wiped out during a Clean Install of XP).
#2) IF, and that's a big "IF ", I was able to do a Clean Install, I would still be using the SAME disk that I've used for the Repair-Reinstalls. I'm pretty sure I'd get the same results, don't you?

You ARE correct! Contacting MS Support is a NON-preferred option. (How perceptive of you! )


Hawk22 !

Unfortunately, the article your link goes to is doesn't really address the issue I'm trying to deal with. BUT, the article is VERY important !

You see, Hawk, the article states that all that is needed is to download and install just one "critical" update and then: "Once you have downloaded and installed at least one critical update from the Windows Update or Microsoft Update web site, Automatic Updates will once again correctly detect, download or install Windows Service Packs or security updates depending on what settings you have selected for Automatic Updates on your computer. "

Generally, I am unable to access MS Automatic Updates because they are getting the incorrect message that I need to "re-boot" my computer before I can download ANYTHING there. Hence: "Error 0x8DDD0007 ". The few times that I was able to sneak past the "Gatekeeper" (Error 0x8DDD0007) and download a few updates, NONE of them would install because they're getting the incorrect message that I need to re-boot my computer first. If I can't install any of those updates, then the MS AU service STILL won't allow me to access the site. See?

So if the MS article (KB-555615) is NOT applicable in my case, then "why" is it SO important???

KB-555615 is important in the "historical sense" of showing the repeated and recurring problems that MS has had (and is currently having) with its attempts to "update/upgrade" the "Automated Updates Service ".

Please note the "Last Review Date" and "Revision Number" for KB-555615.

Last Review : May 26, 2006
Revision : 1.0

The date of 5-26-2006 is noteworthy because it follows MS upgrading their AUS from Version 4 to Version 5 as part of WinXP SP2. That all started in late 2004 and carried over into 2005. With more and more customers finally overcoming their aversions towards accepting one of MS's "Service Packs" (they seemed to remember what happened when WinXP SP1 first came out), the wider-spread adoption of SP2 in late 2005 and early 2006 REALLY brought out apparent problems with the new (v5) AUS. The revision number of "1.0" shows that nobody has ever reviewed, updated, or changed KB-555615 since its original publication!

It is my contention, based on my highly UN-scientific research, that every time MS "upgrades" its "Automated Updates Service ", there is a HUGE upsurge of updating "problems ", "error messages ", and customer complaints !!!

That icludes MS's most recent "Stealth Updates" of July/August of 2007.

Of course, people didn't really know about the "Stealth Updates" until Scott Dunn over at the "Windows Secrets" newsletter (which I've subscribed to for about 4 years) "outed" MS about them. Most people (like me) wouldn't even know that there WAS a problem with MS's AUS until AFTER they did a WinXP Repair-Reinstall! Heck! I remember reading the Windows Secrets article and its follow-ups, but since I was not at that time even contemplating doing a R-R, I took note of the problem, then filed it away in some dusty, cobwebbed area in the back of my brain.

(Which means I read about it, then forgot about it, then re-remembered it AFTER my first encounters with "Error 0x8DDD0007 "!)


Arie !

Thank You for your input! Yes, it just may come to my having to file an "Support Incident ". I don't WANT to, of course, but I just may HAVE to!

BTW : As with the "Windows Secrets" newsletter that I mentioned above, I've subscribed to the "Help With Windows" (Whose new name I can't think of right now...) for the past four years. I signed up when I bought a copy of Registry First Aid. Incidently, I live in Eugene, Oregon (USA) and Rose City Software is located in Lake Oswego, Oregon, about 100 miles north of here. At the bottom of every one of your newsletters, are usually 4 or 5 links to subjects here at WindowsBBS. Which is why, when this past issue ended up in my in-box. I clicked on one of those links and ended up over here!


Anyway, my on-going battle with "Error 0x8DDD0007" continues, and, I must say, it's still going badly for me and my poor computer!

I know that I am (perhaps) holding a a little bit too simplistic view of such a complex problem as Microsoft has created for me.

But, I just want to KILL "Error 0x8DDD0007 ", you know ???

ROBIN
Eugene, Oregon USA

 

OOPS! I Forgot Something !!!

Hello again, Pete !

I forgot to address something in one of your previous replies on this thread!

It has to do with MS KB-943144 (Updates are not installed successfully from Windows Update, from Microsoft Update, or by using Automatic Updates after you repair a Windows XP installation).

I tried both methods many times. Although I was able to re-register the "Wups2.dll" file and DL/Install the "Windows Update Agent" successfully, neither "solution" has worked for me.

I apolgize for leaving that out of my previous post!

ALSO : The registering of various DLL's as described in the "Stealth Updates" article in "Windows Secrets" hasn't worked for me either. I repeatedly tried those (and other combinations of DLL's that I found during my quest) in different sequences, combinations, and modes of operation (Normal & "Safe ").

ROBIN
Eugene, Oregon USA

 

Same Old Disk, Same Old Data, Same Old Results...

Hi, Pete !

Thank You for your quick reply!

I guess my point about doing a "Clean Install ", is that I would be using the same disk that I used for doing Repair-Reinstalls. Regardless of the formatting issue, I would still be using the Same Old Disk, With The Same Old Data, and getting the Same Old Results. See?

And, yes, Arie and you may be right: I might have to submit a "Windows Update Support Incidence" request.


But..... I..... Just..... Don't..... Want..... To..... Go..... THERE.....

ROBIN
Eugene, Oregon USA

 

Maybe... Maybe Not...

Hi, Pete !

"You are assuming that the errant registry entry or whatever is on the install disk - I suggest that there is a better than evens chance that it is not A repair install only overwrites so much and maybe not that entry in the Registry or the source of it. "

Oh, no, not at all !

I'm assuming that it's ALL Microsoft's fault. I have NEVER had anywhere nearas much trouble with a R-R as these times. The only MAJOR difference THIS time around, is with the Microsoft Automatic Updates Service !!!

Go to MS - it's free and they don't bite

Maybe, maybe not. But that won't stop 'em from trying to GUM me to death !!!

 

I've posted a "Widows Updates Support Incident" @ MS

Hi, Pete !

Hi, Arie !

i took a D-E-E-P breath and posted a "Widows Updates Support Incident" over at MS about a half hour ago. I also gave them permission to scan my computer which is STILL on-going.

Will post a copy of my "Widows Updates Support Incident" a little later on today.

Will keep you all posted on how it's going.

THANX !!!

ROBIN
Eugene, Oregon USA

 

COPY of "Widows Updates Support Incident" Report : 3-10-2008

COPY of "Widows Updates Support Incident" Report : 3-10-2008


TITLE : "Error 0x8DDD0007 : Unable to Access Updates After WinXP (Home) Repair-Reinstall "

Hello !

On Tuesday, March 4, 2008, after conducting a needed Repair-Reinstall on my Windows XP (Home) SP1/SP2 Desktop computer, I went to to the Microsoft Automatic Update Services website to download all of the required "Critical" updates needed for my computer.

I was unable to access the updates site and the reason given was "Error 0x8DDD0007 ". I was instructed to "Re-Boot" my computer so I could access the updates site and download any updates. Even though I knew that there were no updates on my computer waiting to be installed, I re-booted my computer and returned to the Microsoft Updates page, where I once again received "Error 0x8DDD0007 ".

This MS Updates behavior has continued (constantly) throughout the past six days. I am reminded every ten minutes to re-start my computer. It doesn't matter how many times I re-boot, the reminders keep popping up.

I have done a few Repair-Reinstalls of WinXp over the past four years and I have NEVER encountered anything like this before. The R-R that I last did on this computer was in March, 2007, and it went as smooth as silk. WHY am I having all of this trouble NOW ???

I have read every KB article that I could find that is even remotely connected to this problem. I have tried (repeatedly) all of the solutions proffered. I have checked the MS Community pages for this and similar "Updates" problems, and tried all of the "solutions" offered there (repeatedly). BUT, none of them have worked.

I have scoured the Internet looking for answers to this. I have visited dozens of "tech" and "help" websites, read hundreds of entries, and tried just about every "solution" I found. Nothing has worked.

This is our one and only computer. We are not on a network. My wife and I are the only two people who use this computer. We both have "Administrator" accounts.

This computer is WGA Validated.
The Windows Download Agent is Installed.
Windows Updates Installer 3.0 is installed.
Windows Updates Installer 3.1 is NOT (re-booting problem...).
.NET Framework 1.0, 1.1, and 2.0 is installed.
.NET Framework 2.0/SP! and newer is NOT (re-booting problem...).

The latest edition of the Belarc Advisor shows that there are 97 Microsoft CRITICAL Updates NOT installed !!!

WHY ???

I have tried dozens of "solutions" and I've tried them multiple times in both regular and "safe" modes.

I've tried the simple Registry "have" of deleting the "RebootRequired" and "Mandatory" sub-folder keys at
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AutoUpdate\RebootRequired\Mandatory.

I have "Registered" any number & combination of DLL's to fix this problem!

I have NOT been able to "Fix" it and it will NOT go away !

Meanwhile, there are 97 CRITICAL updates that I NEED to install on my computer !!!

An article in the September 27, 2007 issue of the "Windows Secrets" newsletter suggests that the source of my Updates "problem" can be traced back to Microsoft and the so-called "Stealth Updates" of July and August, 2007.

I know that MS is aware of the problem because you published KB-943144 on October 26, 2007. The title of KB-943144 is : "Updates are not installed successfully from Windows Update, from Microsoft Update, or by using Automatic Updates after you repair a Windows XP installation "

OKAY... So MS changed it's Updating software and now I can neither access or download and install 97 CRITICAL Updates !!!

PLEASE FIX THIS !!!

Robin @#*&#@#%
Eugene, Oregon USA

PERMISSION WAS GIVEN TO : Automatically collect information

 

Patch Tuesday MS Updates -UPDATES !!!

Hello, Everybody !

Tomorrow (3-11-2008) is "Patch Tuesday ". In addition to the "security" updates, MS is going to be releaseing two or three updates-related "Updates ". Does anyone know what those update Updates are all about ???

I copied the following off of the MS TechNet Advance notification page :

Non-Security, High-Priority Updates on MU, WU, and WSUS For this month:

• Microsoft is planning to release two non-security, high-priority updates on Microsoft Update (MU) and Windows Server Update Services (WSUS).

• Microsoft is planning to release three non-security, high-priority updates for Windows on Windows Update (WU) and WSUS.


Note that this information pertains only to non-security, high-priority updates on Microsoft Update, Windows Update, and Windows Server Update Services released on the same day as the security bulletin summary. Information is not provided about non-security updates released on other days.

The complete page can be found HERE :

http://www.microsoft.com/technet/security/bulletin/ms08-mar.mspx

ROBIN
Eugene, Oregon USA

 

The 9th Time's The Charm !

Howdy, Fellow BBSers !

Well, it took NINE tries but I was finally able to submit a Windows Update Incident Report. Apparently, the 1.2 MB TEXT file Windows Update Log was a little too big to go through the system.

I tried three times on Tuesday, four times yesterday, and twice today. On today's second attempt I decided not to have MS scan for the data. I really think they should have it, but every previous attempt ended with an "Error" page. At least this way, something finally made it through!

Hopefully, my "Error 0x8DDD0007" problem will be resolved some time soon.

Wish me luck !

ROBIN
Eugene, Oregon USA

 

In my experience I have found that not all updates are critical or necessary for my machines. I have a LAN in my home office of 8 machines, used for productivity and LOTS of gaming, and have nothing more than SPK 2 on them. (As far as MS updates go.) I have turned off updates and have never needed anything since. I know this does not fix your problem, nor is this a claim to being able to; it is simply another alternative to beating a dead horse.

 

I normally leave posts with this many replies alone assuming the problem is fixed or on its way...not to say this one isn't. I forced myself to read or scan the posts and get the gist of what is going on...I don't like to do a lot of heavy reading on long posts .

Anyway, I think it was suggested but not sure because of my skimming, that you could just wipe your PC clean and reinstall windows? I don't mean a repair install, I mean the format and install. At this point...if this is a viable option for you, that would be what I would do. Back up data you want to keep, then just format and install winxp again...assuming you have all the correct disks and keys and all that.

Also, this is bugging me...what is AFAIK?

Oh, one more thing. I did see a possibly similar (3 or 4 years ago though so memory is fuzzy) error. It was difficult to find a solution but I found something about a visual basic file that was either corrupt or not there or something. I thought 'visual basic?' what the heck does that have anything to do with windows updates. It did fix the problem though.

Ok, one more...one more thing I want to share. Personally, I would never try install anything beta unless I am doing something cutting edge or it is on a PC I can easily reimage. Leave SP3 beta anything alone if the problem is that you just can't get updates.

I hope none of this sounds condescending...I don't mean it to be that way at all. Good luck with this.