And I just spotted this
"NVIDIA has a fix out for a bad driver update"
windowscentral[.]com/nvidia-has-new-driver-out-fix-old-broken-one
---
I don't know if this will help or be of interest... The way it works over-simplified is that the electronics on the graphics card [or chipset] have X number of capabilities. The companies making those electronics write software to translate instructions from Windows & Direct X into stuff that that graphics hardware can perform. That's one area of glitches & breakage, since not all of the stuff Windows & DX ask can be done, depending on the model & version of the hardware, or maybe it can only be done part way.
With games it gets trickier since developers try to push the envelope, and some of their stuff works, and some doesn't, again varying by the brand & model of graphics hardware. So the folks working on the graphics driver software have to try to fix things by modifying their code in ways that hopefully won't break anything else.
And both of those are what's encountered by gamers running maybe $500 - $1500 in graphics cards, with an additional $1000 - $1500 maybe on the rest of their PC, plus the monitor(s). There Never is a final driver version where everything works -- improving & updating their drivers is a continual process.
Cheaper graphics cards [& on-board GPUs], including mainstream hardware at ~$200 [or more], are often cheaper because stuff is disabled to justify the higher cost of more expensive products. With less capable hardware, less stuff works when it comes to gaming. Add that Nvidia & AMD are less concerned about what works & what doesn't the lower you go on the graphics card ladder, with older & less expensive cards receiving even less attention.
Now with a game like 4 Elements, it uses an older game engine that used a set of Direct X instructions different than what's used with the latest & greatest games. And you could probably guarantee that no one at Nvidia or AMD ever tested their latest drivers with any games of that generation. So when 4 Elements tells the graphics card to do the stuff it needs to do to display the game, it might go so far, processing the commands as they come in, & then something doesn't work and it all just fails.
Why now? It could be that newer drivers just don't process some old commands the way they used to, maybe because some old section of code was removed because it caused problems with newly added code, or maybe changing one or more things in an attempt to fix something with a new game broke the parts that used to work with 4 Elements, or maybe someone just screwed up, which is incredibly easy to do if you're talking parts of the base code that have been there, often ignored or neglected for years. [Old code seldom dies, but just keeps getting added to & added to -- Windows 95 is still there in parts of 10].
The same sort of thing could have happened with the people writing code for Windows 10. It has a lot of compatibility functions & code, & maybe one of the things 4 Elements tells the graphics card to do used to be handled one way for compatibility, but now it's handled some other way, & that way doesn't, maybe never worked with that graphics card.
If one of the Nvidia driver crew were to tackle the problem, to narrow it down as a 1st step they'd likely attach a debugger to get a better idea of what was failing, when. What the more serious gamers do is try different driver versions, test & benchmark, & share their results. I run AMD graphics & at guru3d[.]com the driver threads can run into a dozen [or more] pages per driver release, with folks doing just that.
If you wanted to try & tackle the driver aspect yourself, if nothing showed up using Google, you'd probably use something like DDU [at Guru3d] to remove the current driver in Safe Mode, then when Windows restarts add the next oldest version, & if that didn't work, try the one before that, & so on until you decided to give up. That's what the folks in those threads at guru3d do.
Trying a new download of the game would be faster & easier, but it may lose your saved progress, & might not work either -- the only way it would work is if one of the files had been damaged or removed, or updated in the version you downloaded. OTOH it would install to a MyPlayCity.com folder, so your old copy would still be there -- if you installed the MPC version you could compare the files to some extent without running the MPC game. The MPC version would have extra files for their advertising, while the actual game files may or may not have been altered to handle those ads.
Otherwise you could just try troubleshooting compatibility &/or experiment setting compatibility yourself. Unfortunately one of my constant complaints with 10 is that it's not as consistent as earlier Windows versions. That makes it harder -- what works or worked for Tiffany might work for 6 other people, & fail for 6 other people after that, even if every one of them had identical PCs.
[I've got 3 copies of 10 64 pro on this PC (along with win7) -- 1 main copy, 1 backup, & 1 Insider. The backup copy has graphics driver problems -- the other two are just fine. IMHO yes, you can have a bad copy of 10, or rather a bad installation, everything else being identical & equal. And the AU or build 1607 was a new install of 10.]