n2b

Active Member
Joined
May 18, 2016
Messages
26
I can install all updates in Win-7 successfully except the SP1. Whenever I try it I finally get an error message (Error #80004005). I've tried the automatic fix but that doesn't do any thing. I have also tried to format my C Drive and load a Win-7 (Pro) with SP1 using a DVD from Microsoft. After going through half of the installation I get a message saying that the installation failed with no clue as to why it failed. I end up restoring everything from my back up
I assembled the computer myself from components and was successful in installing Win XP and a few years later upgraded it to Win-7 (pro) with no problems at all. The following hardware are installed
CPU: Intel Core2 Duo CPU E6750 @ 2.66 GHz
RAM : 4.00 GB
32 bit OS
Appreciate any clue as to why the SP1 won't load. Without the SP1 I cannot load IE 11 or get the free upgrade to Win-10
 
Solution
I finally got the SFC /scannow working with no errors, but I still.had the usual problem as before. i.e. halfway through the installation I would get a message that the update to SP1 failed.

I went through the motions of trying to install Win-10 directly like Bigbearjed. But it would not let me since it needed my computer to be at least a Win7-SP1

As a last resort I booted the computer with the DVD and during the installation I chose to format the HD with the reasoning that any corrupted file or registry that may be stopping the installation will be wiped out and I will do a clean install. Half way through the "files expansion" phase I got an error message saying that the installation could not be done due to an unknown reason. Now I...
I could try RichM's suggestion to do a chkdsk /r.
This guide will show a few ways to run chkdsk although whichever method you use make sure you search for and repair broken sectors:
Link Removed

Once the chkdsk has completed then run the SFC as was explained above.
 
Excellent tutorial kemical its the one I usually use. As I know kemical gets this but it needs to be said checkdisk has quite a few different
sequences. I chose "R" because then it not only verfies integrity of the drive and files but can also looks for bad sectors at the surface and can cover over them and or actually hide them from Windows as well as reset all free space for Windows,
 
RichM for information only chkdsk /r dose not check the integrity of the drive
chkdsk /r Locates bad sectors and recovers readable information (implies /F)
wich /f Fixes errors on the disk so no were chkdsk /r dose not check verfies integrity
 
Last edited:
F= fixes disk errors
R= Locates bad sectors and recovers readable information
no disrespect rich but where do you find this words in the R= AND F= (verfies integrity)
I don't understand why you'd need to put extra words into computer commands, it's a bit confusing for someone like me, when you see words that don't belong there, and also gives misconception, and I noticed that you do have that tendencyto do that, like another time when you said (incremental)
which the word belongs only after you have a complete backup, incremental is used when additional information is collected on our drive up to the date of the backup, copying new data as a grows they use the word called incremental. not to be used as incremental updates? it's just not proper I don't mean to be mean this all in good heart
 
In your "good heart" why are you so limited in your use of vocabulary Sandbox?
Here is "dictionary.com" definition of the adjective "incremental":
adjective
1.
increasing or adding on, especially in a regular series:
i.e. small, incremental tax hikes.

Chkkdsk R & F:
chkdsk /f /r or chkdsk /r /f?
scroll all the way down and you will see a list of all switches in checkdisk to improve your limited knowledge on this subject.
All in the spirit of your education!
 
Not more nonsense. This has to stop now. RichM Part of your post I like though is a little insulting questioning Sandboxs vocabulary.

Sandbox, mind the language please and don't insult other users. Stuff like this needs to stop and now. Getting sick of seeing stuff like this on here of late.
 
Move on and stay on topic please.

By the way, in the case of chkdsk, /f used to have to be explicitly called, but this is no longer the case. There is a reason and history for this. It was not always possible to dismount a drive in previous versions of Windows due to the file system and technical limitations of the system. Specifically, at one point, you may recall scandisk was being used instead of the chkdsk from the command-line. Also when you use /r it implies /f and does it anyway. That will end this controversy once and for all. Please do not continue to argue over nonsense.

The original poster deserves a better reply than this madness.
 
Last edited:
Thank you all for your continued interest in my humble but persistent problem with Win7. I will go thru the chkdsk and the SFC as kemical suggested soon - after the holidays. Hopefully we will be able to whip it one of these days
 
Thank you all for your continued interest in my humble but persistent problem with Win7. I will go thru the chkdsk and the SFC as kemical suggested soon - after the holidays. Hopefully we will be able to whip it one of these days
Good luck!
 
Yes let us know how it works out please.
I just reread the whole thread and I think we may have overlooked Holdum333 excellent thought that formatting doesn't touch bad sectors on the drive and the drive being bad is a common reason why Windows installs do not complete....this is more reason than ever to run chkdsk as it might fix it but it also may not complete indicating the hard drive is in poor shape and should be replaced.
The next step after that might be to run one of those hard drive checking utilities on the drive though if checkdisk won't complete I just normally replace the hard drive.
 
Last edited:
Here is the report for the two checks kemical suggested earlier. I ran the chkdsk /r. It completed the 5 stages and at the end very quickly scrolled through the command screen and restarted the computer. I assumed that meant that it did not find any problems.
Next, I did the sfc /scannow. After completing 39% of the scan it stopped with the following message:
"Windows Resource Protection could not perform the requested operation"
What do I do now. As I mentioned earlier, It will not install the Win-7 SP1, otherwise it runs OK and installs other MS security patches etc.
Any suggestions
 
Hi n2b,
have you tried running SFC in safe mode? If not try that .

Suggestion
Also may I ask is there any particular reason your running in 32bit?

I would suggest you back up what you can and then use the page below as well as your activation key to obtain a copy of Windows 7 64bit (it will most likely have SP1 included).
Link Removed

This will also give you the added bonus of being able to use all of the 4GB of RAM too.

Your upgrade to Windows 10, as long as your compatible of course, should be relatively easy.
 
As I wrote earlier I completed the chkdsk /r. It completed with no errors. Next, I did the sfc /scannow. After completing 39% of the scan it stopped with the following message:

"Windows Resource Protection could not perform the requested operation"

I followed up by repeating the scannow, once in normal mode and again in safe mode. Got the same error message at 39% as above.
So I've done everything I can think of short of formatting the whole hard drive and installing Win-7 SP1 from a disc. Which would mean having to reinstall all the applications that I have now -- which I am loath to do if possible.
Question for Kemical for his suggestion that if I have to reformat and install from a disc I might as well go for a 64 bit Win7. If I was to do that what happens to all my application software that are 32 bit. Is there any incompatibility having a 64 bit OS running 32 bit applications? Don't I loose the advantages of a 64 bit OS when the apps are not 64 bit?
 
Hi @n2b I always like to ad my 2cent's to these kind of threads. If you run W7 without upgrading to W7SP1; you PC will be wide open to hackers, updates, and other things which will cause you much grief and will probably end up you stalling W7SP1 from the disc anyway, as @kemical has explained in this thread earlier. The old saying "Pay me now or pay me latter"