I was disappointed not to have had a single response to this enquiry. I would have thought that such a weird fault would have elicited a bit more interest. Never mind.
A bright contributor - drummachine - at the Microsoft Community site came up with an unorthodox but effective solution for users affected by this fault. These are ones using older Intel integrated graphics with driver 220.127.116.1197. The solution is to obtain a copy of the previous version of the library called d3d10level9.dll and place it in the same folder as the affected program's executable. For Windows Live Mail, this would be the one called Windows Live\Mail in the program files directory. For PowerPoint, this would be the appropriate Microsoft Office directory within program files. At the time of writing, the required file was available for download here: d3d10level9.zip
I wonder whether anyone at Intel would care to comment on the fault or its remedy.
Look at the data you collected and then look way, way down this page under "legacy".
You will find that NONE of the graphics are supported and are 10 to 12 years old.
So, you want to know why there is an anomaly in a legacy 32-bit application that has long outlived its usefulness using graphics from chipsets that are 12 years old on a modern operating system using Microsoft's own generic driver? Think about it a bit.
Personally, I think you should be happy that it works at all.
Tell the users to upgrade their hardware to something that is supported on Windows 10.
Al, my field is email. I don't really know the first thing about graphics. I suspect that the users who have experienced this extraordinary phenomenon don't either, with the exception of the one who found the workaround. They were just surprised that something that had been working faultlessly suddenly stopped working after a Windows upgrade. I don't suppose that many of them are concerned about advanced graphics capabilities like those needed for 3D or gaming, for example - if they did, they wouldn't still be using outdated hardware. They just expect the programs they use to work.
I'm typing this on my workhorse machine - a bog-standard Toshiba laptop anno 2010, which soldiers on through update after update and upgrade after upgrade. No, I don't expect it to last for ever, but I hope I can be spared the expense of renewing it for a bit longer. If I took my 1973 Ford to the garage and told the mechanic that it wouldn't start, I wouldn't expect him simply to tell me to buy a Honda - which is analogous to your solution.
I'd rather hoped that someone in the Intel community would at least have some interest in this bizarre fault, regardless of the components involved. I'm sorry to be proved wrong. I'm full of admiration for the user who determined that it was a change in the Direct 3D 10 to Direct 3D 9 translator that caused the fault, and that reverting this change remedied it. I haven't a clue what Direct 3D is or why I need it.
Still, I'm grateful for your response.
My response about upgrading the hardware is very important. Old hardware is not supported. Even Microsoft is abandoning old software at a furious pace. They are even abandoning old forums.
Microsoft even refuses to run anything less than windows 10 on 7th gen and later processors.
So, your Ford - Honda analogy is very flawed.
And, someone from the Intel community (me) did have an interest.