I know, I just considered the information that I had, and didn't consider lack of detailed spec a blocker for the two very basic items of advice that I offered (and I was not intending to get involved at a deeper level than that, so specs would not have helped me assess anything). As I said, I did consider that a PC capable of running ED should not have basic capacity limitations preventing a launcher from updating.
And yes, I agree that self appointed experts on the internet are the worst.... Believe me, when I see advice on the internet, it is filtered to remove errrmmm...'male bovine excrement' at a very early stage

I can recall many instances where suggestions have involved actually making changes to the PC in question, without sufficient information. Even MS forum based support have fallen into this trap. One issue I can think about (but have no intention of recounting here) had the stock advice of either running certain re-installation commands, or just starting with a new Windows user (effectively circumventing a user profile corruption issue). I drilled into what was happening, figured it out how Windows was failing during the build of the user environment, sound a 90% kludge MS had built into windows to prevent the situation from occurring, and how it could fail (allowing profile corruption). The situation was both tragic and laughable at the same time.
I will explain WHY I suggested those two things, then duck out of this thread (possibly excepting clarification requests by the user in trouble).
The logout and restart will ensue the PC is operating for a clean boot, and that any pending updates are fully applied. The logout will likewise ensure that the user environment is rebuilt as cleanly as the current PC config allows. This is always a good first step and does not involve changing anything. Most people do not realise that the boot time optimisations in modern windows versions mean that the OS is cleanly loaded far less frequently than they might imagine.
The security software disable suggestion is not something that I'd recommend lightly, however the wording of the error message suggests some kind of allocation call within the product is failing. It's possible that the hooks that AV/AM products need to inject into the OS are interfering. It has the 'smell' of that kind of issue.
(The other potential cause I was thinking about, was something to do with the dot net framework or the recent update to it)