Endless reboots following update installation

If you can get to the login screen, you can boot to Safe Mode from the Power/Restart options bottom right of screen - SHIFT + left click restart and work through that.

As prompted by the forum, what is your full Windows build number (and hence e.g. from the News section the last update you received?)

(Also available from properties of Windows system files).

Many fixes applied in this 2004 update:
KB4571744 Cumulative Update Windows 10 v2004 build 19041.488 - Sept. 3
E.g.
Addresses an issue that causes a stop error when the initialization of the graphics adapter fails.
Addresses an issue that might cause a stop error (0xC00002E3) at startup. This issue occurs after installing certain Windows Updates that were released on or after April 21, 2020.

If still using an older build, you might consider doing a clean install without accepting updates in the hope your system is then stable - if so, create a disk image, then use e.g. Sledgehammer to block updates, then use it as an update tool as previously mentioned to selectively apply updates.

Consider also manually appply updates in sequence using the links from the News section to identify which one leads to this restart problem.

Another possibility is to try clean installing a later build altogether if now using an older one.

Ideally you can identify this problem to an update- hopefully it's not hardware related and there's no evidence pointing to that, and I hope you're not over-clocking.

It sounds as if there's a crash of some sort rather than, say, sudden and catastrophic thermal shutdown or other hardware failure.

Does Reliability History shown anything? -explore red X's.
Download, install and run Bluescreenview (free). Does that show anything?
Likewise Whocrashed

(These may all be possible in Safe Mode).

In Safe Mode, try disabling your graphics card and NIC - you can use Autoruns (free from MS) if necessary- check boxes. Needs to run as admin.

Try to boot normally again. Any change?

Try uninstalling updates received and rebooting.

Returning to your clean install. If you clean install without accepting updates, and boot without an internet connection, is your system stable? I.e. does it only become stable with subsequent updates?

Check your SSD: Crystal Diskinfo (free) - SMART params.
Hard Disk Sentinel (SSDs too) is the best I know.
Not sure if you can use these in Safe Mode though.

What you might try is to determine your current full build number, then identify each separate subsequent update from the articles in the News section.

You could create a disk image of what you have now for easy reversion.

You can then install the next update in the sequence from that, and see what happens. If ok, update your disk image.
Each article has download links.

Repeat that for each successive update until you identify which is responsible.

This is different to using Windows Update which will typically provide the latest CU.
Also, there could be other updates e.g. drivers, .NET framework...

Yep, crude, but there we are. You migh read the Known and Resolved issues in the article to see if there are any clues.

But as I said, Window Update might have applied other updates too. Remember to use disk imaging each time if you wish to avoid another clean install when it fails.

Here's the most recent for example:


(I searched for 18363 now I know your build)

There will be earlier ones.

Long explanation.

Your currrent build is 18363.592

The numbers after the . increase with every update.

Each update is normally cumulative (potentially includes all the content of the previous updates.

The most recent update given in the News section is 18362.1082.

There are at least these:

657
693
720
836
900
904
959
997
1016
1049

Each article includes a download link.
You could randomly start mid way and see what happens or do each in turn. Your choice.

For example, you could start at the beginning with downloading
18363.657

KB4532693 CU Win 10 v1903 build 18362.657 & v1909 build 18363.657
Note also the reference to the servicing stack update in the text above the link.

Or you could start at a later one and hope to save time.