El Loro Said
"I have Avast Business Cloudcare a/v on my computer. There's a computer shop very near here. Although that's open to the public, it also deals with providing computer support to businesses in the area and that a/v is through them. So not the free one which many people use though there are similarities. I'm aware that one of the scans provided is a boot time scan not that I've ever needed to use it. I assume that's similar to the one in Windows Defender."
I've no doubt of that El Loro, but the issue isn't one of 'software'. It's one of 'hardware'.
"If I discovered that windows update wasn't working and I couldn't sort it out myself I would get that shop to sort it out for me. That did happen once years ago. The latest Windows 10 update last week was successful on my computer."
As the 'update' was also successful on my win 10 box following my actions. However, there shouldn't have been any intervention by myself to facilitate the 'update' on my part.
This isn't a "software" problem, it's a "hardware" problem for o/s providers that want to 'update' their o/s.
Any o/s that provides an 'update' to 'pre boot' activity is 'solid', but following 'the boot' files may well be corrupted.
Did/do you understand the differential between 'software' and 'hardware'?
'Software' enables processes within the o/s. 'Hardware' enables the 'software' to perform it's ability to support an o/s.
Here's the conundrum.
Any 'hardware o/s' system that permits an 'update' must include an 'EEPGROM' which can modify the/that o/s ,so I'm off to bed now.
best regards, Ray Dart (AKA suricat)