SP1 fails to install - code 80004005

[chaoticyeshua]

Hi everyone. I recently built the computer that I am on and installed Windows 7 Ultimate 64-bit in December.

Everything's been working great and no updates have had issues installing until SP1 came out today. It fails every time with error code 80004005, unknown error. I am fairly certain that it is due to the Windows Mail hack, but any attempt to restore the files back to the original versions (I've tried copying them from another machine and sfc /scannow) have not resolved the issue.

On another note, I've read that the same error came up when people did service pack installs for Vista. I have attempted many of the "best practice" fixes for these cases - disabling services, antivirus, startup entries, etc., but this has not resolved the issue, either.

Any advice/suggestions would be great. Thank you in advance!

 

[wds7]

Try these ...:

"Microsoft’s advice is to have users try again, after they either run a troubleshooter or the System Update Readiness Tool , or after disabling any security programs installed on the machine."

System Update Readiness Tool

 

[chaoticyeshua]

Thank you for the reply.

Unfortunately, I've already tried running the System Update Readiness Tool as well. I failed to mention that in my post, sorry! I will try it again though. As for trying the service pack install again, I have tried it multiple times, both through Windows Update and the full installation package downloaded from microsoft.com.

 

[chaoticyeshua]

I tried running the System Update Readiness Tool, rebooting, and installing SP1 again from the full update package, and it failed again with the same error. Any other ideas?

 

[chaoticyeshua]

Anyone have any advice?

I also found out late last night that my wife's PC is doing the same thing. She also has the Windows Mail hack. I'm really thinking this is the cause, I just don't know how to reverse it. Restoring the files from a PC that does not have the hack and running sfc /scannow does not resolve the issue.

 

[Corrine]

Hi, chaoticyeshua.

Did a Norton or McAfee free-trial come preinstalled on the computers when purchased? It has frequently been found that their remnants cause problems with updates.

If so, please do the following:

For McAfee: follow the removal instructions here: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
For Norton: follow the removal instructions here: Download and run the Norton Removal Tool to remove your Norton 2006 product or later version | Norton Support

Next, restart the computer and run the Microsoft Fix it 50202 to reset the Windows Update Components in both DEFAULT and AGGRESSIVE modes. How do I reset Windows Update components?

Shutdown/restart the computer and check Windows Update. First install any Important updates that may be offered and restart the computer. Check again for Service Pack 1.

Note: if you are using a laptop, be sure it is connected to an electric outlet.

 

[chaoticyeshua]

Thanks for your response.

I recently built both this computer and my wife's myself. Thus, the only antivirus we have had installed is Microsoft Security Essentials.

I ran the Microsoft Fix It 50202 in both the default and agressive modes and attempted to install SP1 again. Same error. I am 90% sure this is related to the hack to allow the use of Windows Mail, as detailed in this thread:

http://www.sevenforums.com/tutorials/5481-windows-mail.html

There are no fixes listed on that thread, however, other than formatting and reinstalling Windows. Surely there's another way...

 

[Corrine]

Hi, chaoticyeshua.

From what I have seen, Error Code 80004005 can be caused by a variety of things because it is a generic error code typically associated with "AHH WHAT HAPPENED?" It can be (and is typically) due to other applications behaving poorly. However, I doubt you are the only one who has run the tutorial for Windows Mail, particularly seeing that the topic is 94 pages long.

Although this relates to Windows Vista SP 2, see if it works to solve your problem with Windows 7: Windows Vista and Windows Server 2008 service pack installation fails with error 0x80004005

To work around this issue, turn off the computer and physically unplug all drives that are not required for starting Windows. Power up the computer and restart the service pack installation.

I'm not going to post what the alternative is if this doesn't work.

 

[rfmn482]

Here is my tale of woe :
Have had two failed attempts to install the SP1 update. Both times I get the [COLOR=#0072BC ! important][FONT=inherit ! important][COLOR=#0072BC ! important][FONT=inherit ! important]error [/FONT][COLOR=#0072BC ! important][FONT=inherit ! important]message[/FONT][/COLOR][/FONT][/COLOR][/COLOR] E_FAIL (0X80004005). This error occurs after the install and on the subsequent re-boot. When the computer has nearly re-booted this message appears "Failure converting Service Pack. Reverting Changes.". The re-boot hangs for nearly half an hour before showing my [COLOR=#0072BC ! important][FONT=inherit ! important][COLOR=#0072BC ! important][FONT=inherit ! important]desktop[/FONT][/FONT][/COLOR][/COLOR] with the error message shown above.

I must have spent three hours on this today and don't know what to next.

Please note I do not run Windows Mail so that might be a 'red-herring'

 

[Corrine]

Hi, rfnm482.

Have you tried the suggestions in Troubleshoot problems installing a service pack for Windows 7 and Windows Server 2008 R2? Also note my suggestion to the original poster, to work around this issue, turn off the computer and physically unplug all drives that are not required for starting Windows. Power up the computer and restart the service pack installation.

 

[cartel]

run sfc /scannow

If it doesn't say "did not find any integrity violation" the SP1 wont install.

 

[rfmn482]

Have tried all suggestions on this Forum without success. Have run SFC and received no messages on screen. e.g., "Did not find any integrity violation". Surely this is good news, no!.

The Internet is growing larger by the hour in respect of this problem. Surely Microsoft must take some responsibility and should come up with a quick 'fix'. do they already know about it?.

Having done a fresh install of Windows 7 in mid December I am reluctant to do so again. Would a repair install do the trick?, comments on this welcome.

Have been informed today by two friends that they have the same problem, since I alerted them to the download I feel guilty.

 

[Corrine]

I also found out late last night that my wife's PC is doing the same thing. She also has the Windows Mail hack. I'm really thinking this is the cause, I just don't know how to reverse it. Restoring the files from a PC that does not have the hack and running sfc /scannow does not resolve the issue.

Hi, chaoticyeshua.

Based on the topic linked below, it appears that your initial reaction regarding the Windows Mail hack may have been correct. The instructions Cari received are as follows:

Have you removed/Replaced the WindowsMail from Windows7 with the Vista files to get it working again?

Please start the command prompt (cmd.exe) with admin rights [1] and run sfc [2]:

sfc.exe /scannow

Is it able to find and repair broken files (create the txt file shown under [2] and look if all files are restored)? If not, replace the DLL with the file from your DVD [3].

best regards
André

[1] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token
[2] http://support.microsoft.com/kb/929833
[3] http://blog.nirsoft.net/2009/09/17/how-to-extract-missing-system-files-from-the-dvd-of-windows-7vista/

Apparently the correct version of msoe.dll is dated 7/13/2009.

Cari's topic: SP1 won't install, Error Code 80004005

 

[rfmn482]

Just reporting back to say that I have now managed to install SP1. In the end I did a repair-install of Windows 7 and then installed the Service Pack. This all took a long time (over two hours) but I had spent much more than that trying other 'fixes'. Hope this helps others with the same problem.
Thanks again for all the 'support'.

 

[Corrine]

Thanks for getting back to us, rfmn482.

 

[csadoian]

Windows 7 SP1 will not install if you have reinstated Windows Mail. If you try to install SP1 it will return error 80004005. You can, however, work around this problem by temporarily making a couple of changes to the Windows registry and restoring a .dll file. After SP1 is installed you can reverse these changes so Windows Mail will still work.

This WORKED FOR ME, but your mileage may vary.

First, this workaround assumes you have made the changes to reinstate Windows Mail which involve running the registry patch WinMailEdit.reg and substituting the VISTA msoe.dll file for the Windows 7 .dll. Instructions for doing this are found on this site and in several places on the web.

Go to "%ProgramFiles%\Windows Mail\" folder and temporarily rename the modified msoe.dll file to msoe.dll.new. If you saved the original Windows 7 msoe.dll file when you made the modification you can rename or copy it back to this folder. In my case I had renamed the original file to msoe.dll.org so I just renamed it to msoe.dll. If Windows 7 will not let you access one or both of these files you will need to "take ownership" of these files (again, instructions for doing this are found on this site and on the web).

After you have done this you will need to run this registry patch:

------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de] @="6.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385" Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core.resources_31bf3856ad364e35_en-us_2a7b5bdc414aa532] @="6.1"

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core.resources_31bf3856ad364e35_en-us_2a7b5bdc414aa532\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385" Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core_31bf3856ad364e35_none_b3e2f0d65cd51bcf] @="6.1"

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core_31bf3856ad364e35_none_b3e2f0d65cd51bcf\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385"
---------------------------------
After you do this, restart you computer, then install SP1. SP1 should install without any errors. Restart your computer to complete the update process.

You then need to undo the changes you made so Windows Mail will work. Go back to the "%ProgramFiles%\Windows Mail\" folder and rename the msoe.dll to msoe.dll.org. Because SP1 replaced this file (which is why you get an error 80004005 because SP1 sees a Vista msoe.dll) during the update you will almost certainly need to TAKE OWNERSHIP of the file to rename it. After you have renamed it you then need to then rename the msoe.dll.new (the Vista msoe.dll) to msoe.dll.

Then run this Registry patch to reverse the changes in the registry:

------------------------------------
Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de] @="6.1"

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_67a2bdecbd5f60de\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385" Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core.resources_31bf3856ad364e35_en-us_2a7b5bdc414aa532] @="6.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core.resources_31bf3856ad364e35_en-us_2a7b5bdc414aa532\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385" Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core_31bf3856ad364e35_none_b3e2f0d65cd51bcf] @="6.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-mail-core_31bf3856ad364e35_none_b3e2f0d65cd51bcf\6.1] "6.1.7600.16385"=hex:01 @="6.1.7600.16385"
---------------------------------

Restart your computer and Windows Mail should work as it did before installing SP1.

Chuck​

 

[Bart2010]

Hi Chuck, I am having this exact problem and have not been able to solve it. I have seen many suggestions posted online but yours is a new one. Did anyone try this and did it work for them? I'm just so sick of trying things (a lot of them time consuming) that don't work but if it worked for anyone else I'll give it a go.

BTW running SFC seemed to "undo" the mail hack (re-install the original msoe.dll file) anyway...? However running SFC did not enable the service pack to install for me.

 

[csadoian]

Have you done the "mail hack" to your system? If you have, the fix I have outlined will almost certainly allow SP1 to be installed. If you haven't done the hack then your problem lies elsewhere.

Note that SFC will restore msoe.dll, but it will not restore the registry entries. SP1 checks these, too.

I would advise you to do a restore point first, then reverse the Windows Mail hack as outlined in my post. Reboot and then install SP1. If it still doesn't work then just do a system restore and no harm done other than wasted time.

Chuck

Hi Chuck, I am having this exact problem and have not been able to solve it. I have seen many suggestions posted online but yours is a new one. Did anyone try this and did it work for them? I'm just so sick of trying things (a lot of them time consuming) that don't work but if it worked for anyone else I'll give it a go.

BTW running SFC seemed to "undo" the mail hack (re-install the original msoe.dll file) anyway...? However running SFC did not enable the service pack to install for me.

 

[Bart2010]

Thanks for the reply. I had done the Windows Mail hack which was the problem. In the end I found this post by Gobbledegeek http://www.sevenforums.com/1264388-post958.html, followed the steps exactly and it worked. It seems there are many possible causes to the problem and a lot of solutions- I'm glad I found one that worked in the end. Cheers!

 

[csadoian]

Thanks for the alternate solution. I don't know if it would have worked in my case, but it is certainly easy enough to try. I'll add it to my "database" of workarounds

Thanks for the reply. I had done the Windows Mail hack which was the problem. In the end I found this post by Gobbledegeek http://www.sevenforums.com/1264388-post958.html, followed the steps exactly and it worked. It seems there are many possible causes to the problem and a lot of solutions- I'm glad I found one that worked in the end. Cheers!