Windows 2003 SP1 and SP2 Errors with Windows Update: 0x8007F0F4
I just couldn’t figure it out: after numerous attempts to install Win2k3 Service Pack 1, I continued getting the 0x8007F0F4 error through Windows Update. I read a few newsgroup posts and decided to download the network installation SP1 package in hopes that I was just having trouble with the WU services. No joy…except when using the network install, the error messages I got were even less helpful. No amount of Googling or newsgroup searching seemed to help. After quite a hassle and no effective leads, I was ready to give up on Windows 2003 SP1.
Luckily (or so I thought) Win2k3 SP2 was released and my problems were solved!
Wrong.
The same error was continuing to pop up when using the WU service: 0x8007F0F4
Google and the newsgroups were even less help in relation to SP2. Most problems centered around Windows XP SP2 and the 0x8007F0F4 error, which of course didn’t apply because I’m sure my servers aren’t on battery power.
When I checked the %windir%\WindowsUpdate.log I couldn’t find much to go on except "Update is not allowed to download due to regulation."
Normally, it seems, the "regulation" problem happens when too many clients try downloading patches all at once. That, or your Windows license is invalid. For me, however, the problem occurred over and over, spanning at least a couple months (the log overwrites itself after a while) and I knew our enterprise license was still valid.
I continued getting 0x8007F0F4 errors no matter what time of day I attempted the download through WU. Finally I decided to try the network installation version of SP2 and I finally got a reasonable error message:
Setup has detected that the Distributed Transaction Coordinator (MSDTC) service is disabled. The MSDTC service is required for the successful installation of Microsoft Windows Server 2003 Service Pack 2 (SP2). Please enable the MSDTC service, and then restart the installation of Windows 2003 SP2.For (sic) more information about enabling the MSDTC service, contact your network administrator.
Luckily I was the network administrator and I had a slight clue about the next step. A quick trip to the Services Manager allowed me to set the MS DTC service to "manual" and I was back in business after starting DTC!
Why did was DTC disabled in the first place? The lockdown guide I used a few years ago suggested disabling DTC due to the chance of exploitation. Evidently, you can operate normally for years, receiving every other update except Service Packs, with MS DTC disabled.
I’d love to find out why this is the case. But then again, ignorance is bliss.
Thanks for nothing, MS.
March 29th, 2007 at 1:35 PM
thanks for this.
April 2nd, 2007 at 4:08 AM
Hi,
We are having similar troubles installing SP2 for Win 2003 Sp1. I tried your solution above and it does not seem to be working. I still get the error code - 0×8007F0F4.
Is there any other fix available for this?
MS as usual are of no use.
Thanks,
S
May 18th, 2007 at 10:19 PM
Thank you for posting this solution as it resolved my problem. I am a “Jill of all Trades” but my expertise is networking,not server admin. I could not find the answer on Microsoft’s site and it was quite frustrating so I am thankful you took the time to post this page. Thanks again…Respectfully, Diane
May 22nd, 2007 at 9:01 AM
Thank you for posting this solution. It fixed my problem too. The Distributed Transaction Coordinator service was disabled. Once I set it to manual, Windows 2003 SP2 installed without an issue. I’m not even sure how it got disabled in the first place. I’ve scoured the net trying to figure out how to resolve the issue. Thanks again.
June 11th, 2007 at 1:56 PM
Chalk up another “thanks” from a temporarily stymied installer
I’ve been meaning to look into my SQL 2005 SP install failures, too - perhaps this will also resolve that problem!
June 12th, 2007 at 10:25 AM
Thanks so much! Fixed my problem as well!
July 6th, 2007 at 9:06 PM
Thanks a bunch! Works great now!
September 5th, 2007 at 6:50 PM
I’ve been looking for months for a solution to the problem, Thanks!!!
September 7th, 2007 at 4:08 PM
It worked! Thanks for finding the solution.
September 11th, 2007 at 10:55 AM
Thank you for the info, Microsoft were absolutely useless in suppling an answer.
October 16th, 2007 at 12:13 PM
Your solution worked for us. We had to have SP2 installed before we could install an upgrade for the application running on the server so there is no telling how much time you saved us by posting this info. Thanks!
November 15th, 2007 at 2:52 PM
Thank you!
Is it a surprise that MicroSucks can’t even get their own two products/systems to work together without pissing off the people that pay them dearly for sub-par products? That’s their standard modus operandi.
December 13th, 2007 at 2:01 PM
Thanks for helpin’ a brutha out.
December 14th, 2007 at 9:40 AM
From the looks of it, this isn’t an isolated issue…and I’ve yet to see an acknowledgment from MS regarding this issue. The least they could do is post the fix in their KB!
January 25th, 2008 at 5:55 PM
Thanks a bunch….been trying to figure this one out for a while, especially weird since it only affected 1 of 4 2k3 servers.
February 29th, 2008 at 10:16 AM
Wow! Thanks!
I set the DTC service to Automatic instead of manual, and then I started the DTC service. I am hopeing that this will reduce the likelyhood of a future update failure.
April 29th, 2008 at 4:39 AM
Hey I got a problem with windows2k3 SP2, it says guest.bmp cannot be copied blah blah blah how can i fix this? thanx!