I've been reading that the enterprise version of Windows 10 allows you to better control update shenanigans. I'd rather shoot myself than use Windows 8. Windows 7 is solid, and I am seriously considering going back to it. BUT, I refuse to accept that there's no way to block this from happening on Windows 10.
I understand the anger you feel if this is your software, and Windows 10 is doing this without informing you of how to get it into compatibility, but there is also some responsibility of the software creator to keep up with the current operating systems requirements (I do understand your frustration and I am sure you are sick of answering this question by now). But certainly, aggressively telling a satisfied and happy customer of your software basically that "it's my problem if I want to use Windows 10" isn't very professional and does nothing to solve the problem. If you've written Microsoft to inquire as to what needs to be done to bring your program into compatibility, I'd much rather you tell me that you've submitted an inquiry with microsoft and are waiting for them to tell you how to fix the issue, and that your hands are tied, than being told that I'm stupid and part of the problem.
Gaurav wrote:
The best fix is to use Windows 8.1 or Windows 7. But if you insist on using Windows 10, make sure you are always using the latest version. Currently that's Classic Shell 4.3.0. And updates to Windows 10 can always remove it - that's just Microsoft being unreasonable citing some unexplained "compatibility" reason to remove it. They don't even bother to contact the developer informing what the incompatibility was, if they are removing it. So if despite using the latest version, Windows 10 is removing it then I guess the only way is to reinstall it. Microsoft made unacceptable changes to Windows and if you use it regardless that leaves with no incentive to stop doing such things.