New
#31
VC++ runtime more of them removed only two left repaired and still.
VC++ runtime more of them removed only two left repaired and still.
Uninstalled two versions (x86 and 64) of 2008 redistributable. Option to "Change" did not exist.
"Change" on this one.
I'll report back later.
I have same version 14.38.33135.
- - - Updated - - -
I have same version 14.38.33135. but x64
https://learn.microsoft.com/en-us/cp...?view=msvc-170
Any change?!
So far so good, but I said that before.
After a few days, I may nark it solved (I hope).
Even if this fix works, I still think MS broke something with that update.
Lack of regression testing is my suspicion.
What have You done to fix this problem for now? Please tell me the steps.
That System component Store update I mentioned that references a UWP desktop? There were two VC-related updates such as "Microsoft.VCLibs.140.00.UWPDesktop" and another one without the UWP Desktop part that were installed when this bug showed itself in my system. The plot thickens.
But I haven't had a single error so far, despite using the start menu to shut down every day and interacting with the taskbar. Is it possible that the shutdown prevents the logging of the process crash? I doubt it.
I don't know, but I think it's an interesting coincidence that these VC library updates were installed with the april security updates and shown in reliability history. Usually you can only see the additional packages (like servicing stack) in 'installed updates' of classic control panel. I've never seen this happen before. Note that I skipped march's updates completely, and who knows how long ago it was that I updated the UWP apps through store. Months at least. The Store has been set to never download apps automatically in the background, but that doesn't apparently apply to things marked as system components in Store. Other people may have had those downloaded long before me because they applied the march updates.