If you don't believe me then stop being lazy and ask on the microsoft forums, if you have a MSDN subscription go to support and see what it says. The MFC source has been released & open sourced which gives you a clear indication of the commercial value, it comes free with Visual Studio 17 community edition. You are still on version 14 and have been since 20 July 2015 and they managed the small update to deal with the Windows 10 issues which managed to get released with the last Visual Studio 17 update cycle on 6 March 2018. The update simply deals with legacy MFC calls that stopped working. MFC is targetted to the legacy bridge path it will have no native access to the ever expanding Windows 10 API Calling Windows 10 APIs From a Desktop Application - Windows Developer BlogWindows Developer Blog[^] I should mention the old Win16 API still exist in windows 10 under much the same support and there are a lot of legacy programs that still work and there are also a lot that don't. I love the old 16bit API, I cut my teeth on it but I wouldn't recommend someone write a new development targeting it. So we get into some tricky language about what is and what does support actually mean. I loved the above quote in the article
Or put a different way, there are no secret APIs being kept away from Windows developers.
We could put that another way, we have told you the API and we have no intention of adding it MFC but you can. I will leave you to ponder thru all that and decide if I got it all wrong. I am not microsoft and I don't speak for them so ask them directly. As far as I know your old code will hopefully continue to work on Windows but you will have no access to the new features unless you write them yourself.
In vino veritas