I'm not saying I'm fixed up yet, because my Windows corruption is so deep-seated (the result of multiple heat-related crashes while running Boinc 24/7 for years) that it's going to take several more rounds to fully un-corrupt it, but I seem to have fixed this WSL issue at least

wsl --version
WSL version: 2.7.3.0
Kernel version: 6.6.114.1-1
WSLg version: 1.0.73
MSRDC version: 1.2.6676
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.7291

That, and one other key utility I've got access to, indicate I may finally be in the home-straight of a full-repair, after which I might start addressing how to get docker installed successfully (finally vaguely back on topic)

By coincidence a new update came through for Windows 10 22H2 yesterday, which I installed.
The key utility I got access to is winget, which I only discovered for the first time a month or two back.
It runs in an elevated Powershell (Admin) window and checks your system for low-level updates you wouldn't otherwise know anything about.
Right-click the Start button and select Windows Powershell (Admin)
Type "winget upgrade" to see all out of date apps you have
This will include things like Edge, CPUID, HWInfo, Chrome, Teamviewer etc that you may prefer to update (or not) within their own programs, but it's most useful for updating Microsoft components like WSL
For items that are shown, such as Windows Subsystem for Linux, type "winget install Microsoft.WSL" - the app name being exactly what it displays under the ID heading
Examples I had:
Microsoft.WSL
Microsoft.VSTOR
Microsoft.VCRedist.2015+.x86
Microsoft.VCRedist.2015+.x64

Unless these things get upgraded as part of a Windows Update I have no idea how anyone would know or be able to update them without winget
My WSL --version now reads

wsl --version
WSL version: 2.7.8.0
Kernel version: 6.18.33.1-1
WSLg version: 1.0.73.2
MSRDC version: 1.2.6676
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.7417

What I also discovered, by accident, is that, after a Windows Update that upgrades windows, if I run (again in Powershell (Admin) )
DISM /Online /Cleanup-Image /RestoreHealth
followed by
sfc /scannow
If it reports that it found corrupted files and repaired them, then I immediately reboot, bit by tiny bit I can slightly reduce more and more of my corrupted Windows installation, which then may make it more possible for the rest of it to be put right.
It's a very long and very boring road to travel

Edit: I'm less intending to get the absolute latest versions of apps, though that's a byproduct, as to get known clean uncorrupted versions onto my PC as I'm not sure what parts of the Windows subsystem is broken

---