Am I the only one that has component store corruption after installing Powershell 5.1? Everytime, be it on a real machine or VM, after updating Powershell on 8.1 x64, sfc reports a bunch of Powershell files being corrupt and everytime it says it fixed the issue, it reports the same issue again on another run of the tool.
Thanks, the error is clear enough in the log it seems not detected by SFC in en-us system because Powershell is localized in en-us by default but i did a manual hash check on en-us files and i can confirm the issue Spoiler: technical details this is what i call false-positive SFC issue, similar to what happened in W7 preview rollup just two months ago https://forums.mydigitallife.net/posts/1381686 it happens when a same system file is referenced (or shared) in two different WinSxS components if the file is changed/updated in one component, but not the other, SFC issue occurs in this case, the related files in WMF 5.1 are contained in new component assembly Code: Microsoft.PowerShell.DSCResources.Resources whereas same inbox Windows 8.1 files are contained in slightly different component Code: Microsoft.PowerShell.DSC.Resources hopefully they fix this bug in WMF 6.0 for now, just do not run SFC repair unless you have problems otherwise PowerShell DSC function might get broken
Is KB4040972 needed for satisfy? Cause 2017-09 rollup for .net installing it even after latest framework rollup which KB4041777