sfc/scannow unable to fix some corrupt files

[edassange]

I've run it 3 times but it still can't fix files. I've also tried to place the sfcdetails.txt file on my desktop but after running the necessary elevated command prompt there's no file on my desktop. Any help appreciated.

 

[torchwood]

Hi Ed,
follow this link it will tell you where it is and how to post it here.
http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

Roy

 

[edassange]

Thanks Roy. Yes, that's the guide I followed. Anyway, booted up today and there it is on my desktop. Weird.

Also I'm unable to download this month's Windows Updates but I posted in this section to see if fixing this sorts it out.

 

[edassange]

I would still appreciate some help here.

 

[torchwood]

have you got any W7 disks?
If so follow this link and you can repair the error file
https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=35&cad=rja&uact=8&ved=0ahUKEwi1kMv7jZHMAhVI2BoKHYkXDvU4FBAWCHowDg&url=http%3A%2F%2Fwww.pcworld.com%2Farticle%2F2988539%2Fwindows%2Fif-you-forget-your-windows-admin-password-try-this.html&usg=AFQjCNERI611RK-0rtVlgmkloNsx7TqARw

Roy

 

[edassange]

That's a link to what to do if you've forgotten your login password. As it happens I could have done with that a few weeks ago but that's another matter. I'm guessing I just use the repair option for the sfc scannow issue, is that correct? Thing is doesn't that just fix problems stopping W7 from starting?

 

[torchwood]

If you follow ONLY the 1st section under command prompt, the file will be copied from the disc and replace the bad Utilman.exe file on your system

2016-04-13 19:21:18, Info CSI 0000017b [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-13 19:21:22, Info CSI 0000017d [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-13 19:21:22, Info CSI 0000017e [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2016-04-13 19:21:22, Info CSI 00000181 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"Utilman.exe"; source file in store is also corrupted
2016-04-13 19:21:23, Info CSI 00000183 [SR] Verify complete

Just ignore the rename.

Roy

 

[edassange]

Thanks. Right. It's all making sense now. A few weeks ago I changed my login password and something happened along the way. Anyway what I thought was my new password didn't work, so I did a hack similar to the one you've linked but didn't change things back. So if I repair the file as instructed will I still be able to login? I don't want to go back to the previous password that didn't work.