Sooooo FRSTRATED by win 10 UPDATES

Failed updates will keep repeating without specific intervention, as I guess you know.

You haven't said which update is failing.

Thank you for attempting to state your build number - unfortunately it is incorrectly stated as you've repeated 19042, rather than showing what winver reports as prompted by the forum.

E.g. mine is 19044.1889.

You have build 20H2 (=19042.xxxx).

Check you have at least 30Gb free on C:
Uninstall any 3rd party security software.
Download the current iso file using the media creation tool.
Attempt to upgrade using that as an in-place upgrade, but choose NOT to accept updates as part of the procedure if it gets that far.

Whilst you can try that, it may well fail in exactly the same way.
If it does, you can attempt an in-place upgrade repair of your existing build using a 20H2 iso file.
Given

Now in settings click update & security and the update box opens but doesnt load

this may be appropriate.

Diagnosing upgrade failures can require considerable time, effort (if a volunteer is willing and able), repetitive analysis of logs over some days.

Have you applied any tweaks or hacks or disabled services?

Also post a screenshot of your partitions using a 3rd party partition manager.

Good luck.

The problem there is you're using a 3rd party tool. It's incorrect.

The forum said:


like this:


Or Settings, About.

1. Avoid preview updates - I have Pro so set group policy so I'm not bothered by them
2. KB5016616 is coupled with
KB5012170: Security update for Secure Boot DBX: August 9, 2022

and when one fails the error is usually reported against the wrong update.

In a couple of cases which you can find on tenforums I have asked the user to discriminate between these by
a. pausing WU
b. using WUmgr or WUMT (free, Google) to scan for updates, then try applying 1 at a time.

You should try this, then report the results by starting your own separate thread as your problem is not the same, together with the precise text of any error message.

You are running 21H2, so yours is an update problem.
This thread tries to address what I expect is an UPGRADE issue. Thanks.

Your two issues are fundamentally different as I have explained at some length.

Trying to deal with TWO SEPARATE USERS with DIFFERENT ISSUES in the SAME THREAD is just downright confusing.

Can you understand that?

If you have your OWN new thread.. you will receive the specific advice appropriate to YOUR problem and not someone else's.

I do hope you can understand that.