constant prompt to restart to install updates

Sfkickz · 07 Apr 2015

Windows is constantly prompting me to restart to install updates. When I do, nothing happens. Originally tried troubleshooting it myself with the microsoft help pages, but nothing seemed to fix it. It got to the point where I said, I'll just completely reinstall everything on this laptop to try and get around it, but lo and behold, it re-surfaced 4 days or so after the complete reinstall. It is crazy how many updates I was installing on top of W7 SP1. At this point, i've begun considering just upgrading to W8.1, but I just have been very happy with W7 so I'm attached and would prefer not to just redo the same reinstallation process plus find new drivers(do they even have em for some of my components?) for this laptop.

Windows Update Diagnostic:
Attachment 355390
Attachment 355391

NoelDP · 07 Apr 2015

The CheckSUR results are only partial ones - either the tool crashed before completion, or you didn't wait for it to complete.
The SFC scan is also incomplete in the CBS.log
There are no significant errors within the CBS.log

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

Sfkickz · 08 Apr 2015

updated: there's the windowsupdate.log in the .rar and a more recent one attached

NoelDP · 08 Apr 2015

What 'rar'?
Please follow the instructions!
Having said that, there are no errors in SFC. CBS, or CheckSUR logs.
As far as the WU log is concerned, it may take a while to dissect it, but at first blush, all the problems appear to be the result of internet connection problems.
PLease fill in your system specs - the more detail the better!

A look at the Event logs may help...

Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.

Sfkickz · 14 Apr 2015

NoelDP said:

What 'rar'?

I had mistakenly uploaded a .rar, but had forgotten i had changed it to .zip

I decided to do another clean reinstall since I had been coming to the end of my rope and this is my only pc at the moment. the issue hadn't affected the functioning of the system besides not updating and constant prompts to "restart to install updates," but it bothered me nonetheless.

since you mentioned connectivity problems in the log, I opted to use an Ethernet cable (who knows how the university has the network set up). installed windows 7 SP1 from disc with no issues: though opted not to enter a serial key and activate it since i had noticed some weird prompts about checking if my windows was genuine before these issues arose (it certainly better be). immediately installed the LAN driver and ran the SURT hotfix. after restart, told windows update to download updates, but prompt me to install. checked and ran 180 or so, restarts and all. then went through a bunch more cycles of smaller batches. a few more hours later, i sitting here with 203 windows 7 updates and a fresh laptop with all my drivers, programs and settings. The process I followed seemed to have bypassed the problem updates and I am now completely up-to-date.

now i'm curious what caused the SURT to be developed because it seems to have affected my ability to reinstall and completely update windows 7 SP1 from my disc.

after writing all this, i'm suddenly worried about my windows license key. crossing my fingers and hope it works when I decide to try and activate (got 30 days)

NoelDP · 15 Apr 2015

CheckSUR is merely a large collection of the files most commonly found to be corrupted, according to the telemetry results sent back to MS. They are packaged in a wrapper that checks for corruption and attempts to fix it using the files it has - and lists all found corruption, and the results of fix attempts.
It doesn't normally 'change' anything - it simply attempts to return the filesystem and registry to its normal state.