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 (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story