thomas dubreuil
New member
- Jan 21, 2016
- 2
Hello, I ran sfc /scannow on my machine and I'm stuck in a loop, sfc keeps repairing same files under C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US,
alternating between 2 different store "sources".
1st scan:
sfc found corrupt files in C:\Windows\SysWOW64\Printing_Admin_Scripts and repaired/link to:
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.17763.1_en-us_09c7f42dd8da8073 (dated 15/09)
2nd scan:
When running again sfc find same corrupt files and repaired link to
C:\Windows\WinSxS\x86_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.17763.107_en-us_27848dcd197a9515 (dated 29/10), which is the good one/original for this release (17763.107)
sfcfix.exe does not find any corruption (there isn't any in fact), I have done checkhealth, restorehealth and a repair install already...
I know it can be safely ignored as it looks like a "false positive", but I'd love to fix it anyway (or know if it's not possible).
I attached cbs.log with the 2 scans in a row and sfcfix.txt
Upgraded to 17763.134 and now .165, still same error.
Thank you in advance,
Thomas
alternating between 2 different store "sources".
1st scan:
sfc found corrupt files in C:\Windows\SysWOW64\Printing_Admin_Scripts and repaired/link to:
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.17763.1_en-us_09c7f42dd8da8073 (dated 15/09)
2nd scan:
When running again sfc find same corrupt files and repaired link to
C:\Windows\WinSxS\x86_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.17763.107_en-us_27848dcd197a9515 (dated 29/10), which is the good one/original for this release (17763.107)
sfcfix.exe does not find any corruption (there isn't any in fact), I have done checkhealth, restorehealth and a repair install already...
I know it can be safely ignored as it looks like a "false positive", but I'd love to fix it anyway (or know if it's not possible).
I attached cbs.log with the 2 scans in a row and sfcfix.txt
Upgraded to 17763.134 and now .165, still same error.
Thank you in advance,
Thomas