Sign in with
Sign up | Sign in
Your question

Windows 7 - same 5 updates repeating download on every shut down.

Last response: in Windows 7
Share
January 21, 2013 10:13:54 AM

They are all microsoft .net updates.
I have tried the microsoftfixit tool and also tried repairing the .net file and then re downloading the updates after. But annoyingly they pop back up every time.
Anyone have a clue as to how I resolve this issue?
Thanks in advance.
a b $ Windows 7
January 21, 2013 12:06:07 PM

It will be helpful to know which 5 updates.
a b $ Windows 7
January 21, 2013 12:11:13 PM

Try to update them one at a time.
Related resources
a b $ Windows 7
January 21, 2013 12:27:40 PM

numpteyman said:
They are all microsoft .net updates.
I have tried the microsoftfixit tool and also tried repairing the .net file and then re downloading the updates after. But annoyingly they pop back up every time.
Anyone have a clue as to how I resolve this issue?
Thanks in advance.


Are they the same updates every time? Also, do they report as failed or success?

If they are the same updates, and they repeatedly report as failed, this is usually because you have a corrupted system file.

Run CMD.EXE as an administrator, and run this command: SFC /SCANNOW

It will take a while, and require a restart when completed. If the updates don't install after that, you will probably have to reinstall the operating system from your original discs (if you choose "repair" during the reinstall, it may fix the problem).

This is caused from one of two things:
1) The system being shut down unexpectedly (abnormal shutdown)
2) The hard drive is failing

I have noticed several hard drives die a slow death - creating intermittent problems before reporting something that identifies defective hardware.
a b $ Windows 7
January 21, 2013 1:14:19 PM

Download and run CCleaner and tell it remove windows updates.

Then check for updates, sometime you get corrupt ones that just won't install or go away.
January 22, 2013 10:15:22 AM

Thanks for your help everyone but it seems to have resolved itself. Must have been a problem that was being worked on by Microsoft. Again thanks for your help.
!