Stuck on "Checking for Updates" in Windows 7

[mrmike16]

Windows 7 Pro x64

This is a brand new build.
I tried every suggestion I could find, including formatting my PC.
Windows Update updated the Windows Update Agent itself, but after that just gets stuck on Checking for Updates.
This even happens when upgrading to Windows 10 via the tool from Microsoft; it downloads 10 and then gets stuck on Checking for Updates.

I never had this problem before.
Antivirus is disabled.
Clean install, still happening.

I am aware there are tons of updates. But NEVER has it taken this long, and I have installed Windows 7 many times. And this computer's network is faster than any of them.

And people say 10 is buggy xD

Please help ASAP. Thanks

This event log might help:

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: 3/19/2016 3:42:19 AM
Event ID: 4107
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NEOTERIC-Antec
Description:
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
<EventID Qualifiers="0">4107</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-03-19T07:42:19.033810600Z" />
<EventRecordID>742</EventRecordID>
<Correlation />
<Execution ProcessID="1424" ThreadID="4416" />
<Channel>Application</Channel>
<Computer>NEOTERIC-Antec</Computer>
<Security />
</System>
<EventData>
<Data>http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab</Data>
<Data>A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
</Data>
</EventData>
</Event>


The computer clock states the correct time and date. So, not sure what it meant.

If I can't fix this, I'll have to resort to using Linux >.<

 

[techgeek]

Have you tried running the System File Checker?:

sfc /scannow

 

[mrmike16]

Have you tried running the System File Checker?:

sfc /scannow

Does Windows 7 have that?
When I put that in Run, it opens a CMD prompt for a split second and disappears.

I've used it in 8.1 and 10...didn't think 7 had it.

 

[Rabmac]

I normally find that the best think to do is just leave it alone and it will complete. I have seen some PCs take over 12 hours to complete the check on a fresh install.

My advice would be to leave it for 24 hours if it does not complete in that time you usually have a problem. If this is the case, as Techgeek said run: sfc /scannow in the command prompt. I suggest doing this is safe mode.

 

[mrmike16]

I normally find that the best think to do is just leave it alone and it will complete. I have seen some PCs take over 12 hours to complete the check on a fresh install.

My advice would be to leave it for 24 hours if it does not complete in that time you usually have a problem. If this is the case, as Techgeek said run: sfc /scannow in the command prompt. I suggest doing this is safe mode.

I'll take your advice, then. I'll keep you posted.
Thanks for the replies so far!

 

[TheBeerAddict]

Im usually getting these errors with windows update and for me it didnt worth the time ive spent to fix it everytime...So i came up with this tool that downloads updates from the official microsoft servers ,gathers them and the only thing you have to do is execute the .exe in the folder.Just wait patiently for it to complete (cause the updates are going to be for sure above 100)...

http://download.wsusoffline.net/ Theres also a tutorial on the site!

If you want give it a try...i didnt regret it!

 

[mrmike16]

Thanks for the help everyone. It worked after 10 hours of waiting...which was REALLY weird. But now it's updating normally, and currently upgrading my PC to Windows 10 (Since I have a volume license, I can't go straight to 10).

 

[techgeek]

Just FYI, yes sfc works in Windows 7, you have to run if from an elevated command prompt.

 

[Rabmac]

Glad it is working now mate, you may have a second round of updates but usually after 2 big runs it is normally only minor updates. (this is true for Windows 7 anyway)

 

[mrmike16]

Glad it is working now mate, you may have a second round of updates but usually after 2 big runs it is normally only minor updates. (this is true for Windows 7 anyway)

Windows 10 actually only had 2 minor updates. Must have updated itself in that 15 minute upgrade from 7 (SSDs rock!!!). But it lost the network driver somewhere along the way...it's all good now! FYI those eyes on your picture are so creepy xD

About the SFC thing- Good to know!

 

[Rabmac]

haha