D
Davidk03
This is a story about the impact/issues of Visual C++ redistributables in a win10 upgrade. And a request about ameliorating an issue.
I use Corel Video Studio (VS: a video editor program) extensively. Each version (a new one annually, 2 or 3 service packs in between) makes considerable use of MS Visual C++ redistributables, by year and in several versions (x86 and x64, each with different version numbers). A single version may use 4 or 5 of them. See screenshot for 5 versions of VS on a win7 PC
The VS program allows several different versions to be installed on the same PC, altho only one can run at any one time. And the program runs with same constraints under windows 7 and 10 (Corel spec, and reports from various other users).
Under windows 7, I have 5 versions of VS installed (for reasons related to class tutoring), and they all run consistently. I've tried upgrading to windows 10 3 times, and on 2 of those times I aborted the upgrade and reverted to win 7 because of issues with VS that I traced to the use of C++redistributables. It's been an immensely frustrating experience.
Upgrade try 1 - was using the MS recommended in-place method. After it was done, each VS version opened correctly, but at a specific place where modes changed (Edit to Share), the program failed to complete a screen panel action correctly: it hung up. And in that condition that only escape was using task manager to kill the program. Every VS version responded in an identical way. Various actions like driver regressions etc did not rectify the issue.
Upgrade try 2 - was a clean install of windows 10. Once done, I re-installed VS, and this indicated the source of the issue when VS requested permission to download the re-distributables. Installed, program ran correctly. I researched this and found that 1) MS recommended that re-dist run under the same runtime as they were created for, and 2) the runtime, part of the OS, is quite different between win7 and win10. And the re-dist versions installed under win10 were quite different versions to those installed under win10. Further research: MS stated it tries to update each re-dist when OS changes or version updates occur. I abandoned this upgrade attempt for "other reasons", but it identified what was wrong with the migrated VS installations, and showed a path to success with VS and re-distributables.
Upgrade try 3 - was an in-place upgrade (to address the "other reasons" from try 2). When done, I completely uninstalled every version of VS, and all its plug-ins, and every version of C++ redistributable showed in the P&F listing. Tedious to say the least. After that was done, clean up, using cclean including the registry, and re-boot. Installed 2 versions of VS, oldest one first, and after each one, checked that the previous screen panel issue in that version had been fixed; it was. But then I noted that after the latest install, and correct screen panel operation was OK, a check of the older version showed it had reverted to the hung condition. It looked very like the C++ redistributables worked on the latest version of VS installed.
Very frustrated, I used a backup to recover to win 7 where everything works fine. Starting from a clean install, or a new PC, running win10, multiple versions of VS are running elsewhere without this issue. Which is what I had hoped to emulate.
So, the question(s?) is/are what could cause the C++ re-distributables to act like this? Is there something that was necessary that I did not do when cleaning out the win7 and C++ redistributable components?
Continue reading...
I use Corel Video Studio (VS: a video editor program) extensively. Each version (a new one annually, 2 or 3 service packs in between) makes considerable use of MS Visual C++ redistributables, by year and in several versions (x86 and x64, each with different version numbers). A single version may use 4 or 5 of them. See screenshot for 5 versions of VS on a win7 PC
The VS program allows several different versions to be installed on the same PC, altho only one can run at any one time. And the program runs with same constraints under windows 7 and 10 (Corel spec, and reports from various other users).
Under windows 7, I have 5 versions of VS installed (for reasons related to class tutoring), and they all run consistently. I've tried upgrading to windows 10 3 times, and on 2 of those times I aborted the upgrade and reverted to win 7 because of issues with VS that I traced to the use of C++redistributables. It's been an immensely frustrating experience.
Upgrade try 1 - was using the MS recommended in-place method. After it was done, each VS version opened correctly, but at a specific place where modes changed (Edit to Share), the program failed to complete a screen panel action correctly: it hung up. And in that condition that only escape was using task manager to kill the program. Every VS version responded in an identical way. Various actions like driver regressions etc did not rectify the issue.
Upgrade try 2 - was a clean install of windows 10. Once done, I re-installed VS, and this indicated the source of the issue when VS requested permission to download the re-distributables. Installed, program ran correctly. I researched this and found that 1) MS recommended that re-dist run under the same runtime as they were created for, and 2) the runtime, part of the OS, is quite different between win7 and win10. And the re-dist versions installed under win10 were quite different versions to those installed under win10. Further research: MS stated it tries to update each re-dist when OS changes or version updates occur. I abandoned this upgrade attempt for "other reasons", but it identified what was wrong with the migrated VS installations, and showed a path to success with VS and re-distributables.
Upgrade try 3 - was an in-place upgrade (to address the "other reasons" from try 2). When done, I completely uninstalled every version of VS, and all its plug-ins, and every version of C++ redistributable showed in the P&F listing. Tedious to say the least. After that was done, clean up, using cclean including the registry, and re-boot. Installed 2 versions of VS, oldest one first, and after each one, checked that the previous screen panel issue in that version had been fixed; it was. But then I noted that after the latest install, and correct screen panel operation was OK, a check of the older version showed it had reverted to the hung condition. It looked very like the C++ redistributables worked on the latest version of VS installed.
Very frustrated, I used a backup to recover to win 7 where everything works fine. Starting from a clean install, or a new PC, running win10, multiple versions of VS are running elsewhere without this issue. Which is what I had hoped to emulate.
So, the question(s?) is/are what could cause the C++ re-distributables to act like this? Is there something that was necessary that I did not do when cleaning out the win7 and C++ redistributable components?
Continue reading...