|I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP.
When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible).
See Bad Start Menu[^]
There are lots of error entries in the Event Log like:
EventLog Example 1[^]
EventLog Example 2[^]
EventLog Example 3[^]
EventLog Example 4[^]
The program, itself, seems to operate correctly!!!
Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10.
To my surprise, the symptoms were the same!
(I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.)
For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications.
I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why.
Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" to use, etc?
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton