Hi Andrew,
Thanks, that was fast.
I'm looking to upgrade to win10. Tried 3 times so far, and each time the new win10 whilst running has buggered something different in my software environment. The easiest way to avoid problems with a 4th attempt is to get rid of these C++ re-distributables
first. I was trying to avoid a rundown on how I came by that conclusion, painful . . . . but some of it seems necessary, see below.
So, this is what the re-distributables on my PC currently look like

And that link you sent really doesn't cover the problem; apart from anything, there are more re-distributables earlier than 2010 than afterwards. And these programs are associated with/installed by Corel's video studio program. And while that link identifies
the folder the redistributables are in (/winsxs), the folder names in it are so convoluted and unrelated that it is pretty near impossible to identify any re-distributables there.
My buggered updates, and why?? research identified that the re-distributables used under win7 are different to those under win 10: they simply won't work, and MS has reported that in various pages I found on the net. And removing the migrated win7 versions
under win10 and then re-installing the related Video studio program which in turn installed win10 re-distributables partially solved the issue, but made it look like the redistributables under win10 had been captured by the latest program version installed:
VS allows several version on the same PC, but only one can run at the same time. Running installed version x10, worked, but the installing/running version 2018 (version is 1 year later than x10) worked, but the x10 version broke at a place where redistributables
are known to be in action.
I can onbly conclude that something associated with redistributables seems to have carried over in the upgrade.
The fix seems to be to remove everything related to re-distributables before attempting an in-place migration: so the win10 installation starts with a clean slate. And thus my opening query: about clean up, and specifically whether there is something else
apart from delete them in P&F that must be done, and I suspect the registry is involved here.
Is there something else??