Twincam
Member
"sfc /scannow" unable to fix corrupted files - "Vista Business" x86 SP2
Hi Sysnative,
I located you via Google (searching for "winsxs issues) and noting that I have a similar problem (on a friend's Laptop) to several of the solved postings on here. Aged, but otherwise OK Acer TravelMate 7730, in which I have just replaced the failing HDD (using BartPE-based Ghost image). Was about to return PC (everything works OK - I have installed all available "Windows Updates") but decided to run "sfc /scannow" and it detected corruption ....
Rebuilding "winsxs" is (certainly!) beyond me, but I would hate to return a PC with potential future problems. I noted that there is no actual "Pending.xml" file but there are 10 files prefaced with a long number and a ".pending.xml" extension. I have a "Vista Ultimate" x86 SP2 virtual machine available (which has run "sfc/scannow" - with successful fixes) in case that helps. I have also downloaded the "CheckSUR" tool (KB947821 v35) in case I needed it. I did attempt to use it (unsuccessfully) and it highlighted the fact that, after migration from the (failing) Toshiba HDD to the new Seagate HDD, I had to install a newer Intel IRST driver (a geometry issue - not obvious). Doing that fixed the then non-running "Windows Search" service and allowed me to run the then non-running "Windows Update" service. Everything is now (apparently) OK - in fact running very well for an old Laptop - but I know it could be only a question of time .... and that the 10464 files in the "PendingRenames" folder are probably redundant. Some date back to November 2013! There is an additional folder in winsxs\Temp with a long numeric name. It contains a single file created in April 2010!
Thanks for this (and I hope I made my first post correctly!).
Cheers, Neil.
Hi Sysnative,
I located you via Google (searching for "winsxs issues) and noting that I have a similar problem (on a friend's Laptop) to several of the solved postings on here. Aged, but otherwise OK Acer TravelMate 7730, in which I have just replaced the failing HDD (using BartPE-based Ghost image). Was about to return PC (everything works OK - I have installed all available "Windows Updates") but decided to run "sfc /scannow" and it detected corruption ....
Rebuilding "winsxs" is (certainly!) beyond me, but I would hate to return a PC with potential future problems. I noted that there is no actual "Pending.xml" file but there are 10 files prefaced with a long number and a ".pending.xml" extension. I have a "Vista Ultimate" x86 SP2 virtual machine available (which has run "sfc/scannow" - with successful fixes) in case that helps. I have also downloaded the "CheckSUR" tool (KB947821 v35) in case I needed it. I did attempt to use it (unsuccessfully) and it highlighted the fact that, after migration from the (failing) Toshiba HDD to the new Seagate HDD, I had to install a newer Intel IRST driver (a geometry issue - not obvious). Doing that fixed the then non-running "Windows Search" service and allowed me to run the then non-running "Windows Update" service. Everything is now (apparently) OK - in fact running very well for an old Laptop - but I know it could be only a question of time .... and that the 10464 files in the "PendingRenames" folder are probably redundant. Some date back to November 2013! There is an additional folder in winsxs\Temp with a long numeric name. It contains a single file created in April 2010!
Thanks for this (and I hope I made my first post correctly!).
Cheers, Neil.