Mark,
if you can get to it, have a look in the event viewer to try to ascertain whether something is failing.
The reason I suggest it is that I've had a very similar problem on a couple of machines, which I think in my case was caused by the installation of a couple of oldish 3rd-party programs.
I identified a failing module, but never did find the absolute root cause (carefully installing the offending programs in a different order after a full re-image seemed to finally resolve it).
Other people have reported similar symptoms, with the same failing module, with different potential causes, and absolute nightmares trying to resolve. At the time there were no Microsoft recommended remedies.
The failing module was (from my memory) "Edgehtml.dll" which, as might be gathered, is part of the HTML renderer for the Edge browser. The issue is that an awful lot of the other Microsoft function is rendered by this, not just Edge. In addition, a lot of 3rd party stuff takes the same path.
So, you invoke a function from the start menu, it appears to initialise, and then just crashes. Virtually nothing is invokable. I must have managed somehow to get into event viewer, because the evidence was there, but I can't remember how easy it was.
(I have to say that I doubt "new" Edge, released pretty recently, uses the same rendering engine, but I doubt that the core Windows function will have moved away from it)
Last edited by: tyrednemotional on Sun 19 Apr 20 at 17:12
|
