OpenSource Ghost
Member
1. Retail VC++ libraries (https://aka.ms/vs/17/release/vc_redist.x64.exe) are for non-UWP, legacy software
2. AppX VC++ UWP (Microsoft.VCLibs.140.00.UWPDesktop) libraries package is located in "Windows\Program Files\WindowsApps" and is for non-system UWP apps that are also found in "Windows\Program Files\WindowsApps"
3. AppX VC++ (Microsoft.VCLibs.140.00) libraries package is located in "Windows\Program Files\WindowsApps" and is for system UWP apps that are found in "Windows\SystemApps" , where each VC++ library file always ends in "_app" (such as concrt140_app.dll)
Questions:
- Do any packages other than the ones found in "Windows\SystemApps" use VC++ library files that end in "_app" ?
- VC++ "_app" library files for packages in "Windows\SystemApps" are very out-dated. Is it possible that the out-dated "_app" library files "Windows\SystemApps" act as links to newer "_app" library files found in "Windows\Program Files\WindowsApps" or that Windows simply ignores the out-dated "_app" library files and uses newer ones if they are present in "Windows\Program Files\WindowsApps" ?
I don't have a way to figure it out for now, but with Process Monitor or System Informer or any other advanced task manager it should be possibly to inspect handles and threads of executable images found in "Windows\SystemApps" directory to see if they ignore the old out-dated "_app" files packed with them and use newer "_app" library files found in "Windows\Program Files\WindowsApps"
2. AppX VC++ UWP (Microsoft.VCLibs.140.00.UWPDesktop) libraries package is located in "Windows\Program Files\WindowsApps" and is for non-system UWP apps that are also found in "Windows\Program Files\WindowsApps"
3. AppX VC++ (Microsoft.VCLibs.140.00) libraries package is located in "Windows\Program Files\WindowsApps" and is for system UWP apps that are found in "Windows\SystemApps" , where each VC++ library file always ends in "_app" (such as concrt140_app.dll)
Questions:
- Do any packages other than the ones found in "Windows\SystemApps" use VC++ library files that end in "_app" ?
- VC++ "_app" library files for packages in "Windows\SystemApps" are very out-dated. Is it possible that the out-dated "_app" library files "Windows\SystemApps" act as links to newer "_app" library files found in "Windows\Program Files\WindowsApps" or that Windows simply ignores the out-dated "_app" library files and uses newer ones if they are present in "Windows\Program Files\WindowsApps" ?
I don't have a way to figure it out for now, but with Process Monitor or System Informer or any other advanced task manager it should be possibly to inspect handles and threads of executable images found in "Windows\SystemApps" directory to see if they ignore the old out-dated "_app" files packed with them and use newer "_app" library files found in "Windows\Program Files\WindowsApps"