If you had this much stuff archived when going from Version 1607 to Version 1703, and it's not "ancient" then I'd strongly encourage you to submit feedback to Microsoft through the Feedback Hub and to the makers of your software.
At this juncture I lay more of the blame on the software makers than Microsoft, since the tweaks necessary to make code identify itself as "Windows 10 compatible" were well-documented and available to developers long before July 2015, and if they want to be an ongoing part of the Windows ecosystem they should have been integrated by now (long before now, actually).
Angry customers aren't something any business likes.
Edited by britechguy, 06 August 2017 - 10:28 PM.
Corrected typo of "1603" to "1703"
Brian AKA Bri the Tech Guy (my website address is in my profile) Windows 10 Home, 64-bit, Version 1709, Build 16299
Here is a test to find out whether your mission in life is complete. If you’re alive, it isn’t.
~ Lauren Bacall