24H2 makes Windows hate fetching updates

I completely clean installed 24H2 and there seems for be something wrong accessing any MS update server.

- Windows Update doesn't automatically scan for updates, clicking Scan makes it search for updates forever. I manually had to install the standalone MSU files.
- The MS Store doesn't find new app updates.
- When opening an MS Store app that informs me there's a newer version for this app (such as Sound Recorder), it gets stuck forever downloading the update.
- The "Hide Updates" Troubleshooter also gets stuck at scanning for updates. Even though it's deprecated it always worked for me until now.

No problems using the browser visiting webpages.

Never had this before and no idea what the cause might be.

It’s not uncommon for MS servers to be flakey. Try again in a few hours and see. Or has this been going on for days?

antspants said:

It’s not uncommon for MS servers to be flakey. Try again in a few hours and see. Or has this been going on for days?

Click to expand...

You are right, the next day everything worked normally again. It was a very bad timing with me clean installing 24H2 which made me suspicious.

If I had to guess, I'd bet that either the time or time zone were incorrect since this would cause exactly the symptom you described.

I don't recall how much of a skew is acceptable, but there is a possibly that the error eventually got corrected when time synchronization took place.

I cannot prove that this is what happened now, but it is a distinct possibility.

UPDATE: As I noted previously, I don't know how accurate time needs to be for Windows updates or Microsoft Store updates to function properly, but Kerberos requires accuracy within 5 minutes. My guess is that it would be similar for Windows updates or Store updates.

I disagree with the premise that 24H2 is conclusively to blame. I think that is a not easy to prove. These types of issues have been in Windows going back a number of years.

Re issues with apps in the MS Store that don't update that can be an issue at MS end or can be sometimes be fixed by going a repair install or reinstalling the app if possible.