Computer gurus/ IT professionals please help

[russian rocket]

hey guys, i need some help with my computer. the other day my computer did a windows update and upon reboot, it said it failed to start and booted into the windows repair. it tried to repair itself but said it failed. after multiple attempts, i tried to do a restore point, it said it was succesfull but still would not boot windows, kept on going back to the windows repair.

i tried to do the sfc scan but it kept on telling me that it could not start because there was a repair in progress and i would need to reboot.

i then booted from windows cd and ran cmd and tried the sfc scan again but same thing.

so i removed my hard drive and through a sata to usb adapter hooked it up to my wifes laptop. finally was able to run the sfc scan. it scanned but it too was unable to repair the corrupted files. in the log it gives me this:

 

POQ 137 ends.

2015-05-19 18:22:53, Info CSI 00000335 [sR] Verify complete

2015-05-19 18:22:53, Info CSI 00000336 [sR] Repairing 1 components

2015-05-19 18:22:53, Info CSI 00000337 [sR] Beginning Verify and Repair transaction

2015-05-19 18:22:53, Info CSI 00000338 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :

Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-05-19 18:22:53, Info CSI 00000339 [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-05-19 18:22:53, Info CSI 0000033a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :

Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-05-19 18:22:53, Info CSI 0000033b [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-05-19 18:22:53, Info CSI 0000033c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :

Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-05-19 18:22:53, Info CSI 0000033d [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-05-19 18:22:53, Info CSI 0000033e [sR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"

2015-05-19 18:22:53, Info CSI 0000033f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :

Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-05-19 18:22:53, Info CSI 00000340 [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-05-19 18:22:53, Info CSI 00000341 [sR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"

2015-05-19 18:22:53, Info CSI 00000342 Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :

Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-05-19 18:22:53, Info CSI 00000343 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :

Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-05-19 18:22:53, Info CSI 00000344 [sR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted

2015-05-19 18:22:53, Info CSI 00000345 Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :

Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-05-19 18:22:53, Info CSI 00000346 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :

Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-05-19 18:22:53, Info CSI 00000347 [sR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted

2015-05-19 18:22:54, Info CSI 00000348 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

 

i really dont know where to go from here, i read that the update might be causing a lot of issues, can i access the update through the hard drive system files and delete it like that?

any help will be much appreciated, thanks!

[Exodus]

Is this a test? If I pass, will you hire me at the NSA?

 

I would go into safe mode and uninstall any windows updates you have installed recently.

 

Also, Check out this link:

 

http://thetechcookbook.com/windows-7-update-kb3022345-causing-corrupt-files/

[russian rocket]

Is this a test? If I pass, will you hire me at the NSA?

 

I would go into safe mode and uninstall any windows updates you have installed recently.

 

Also, Check out this link:

 

http://thetechcookbook.com/windows-7-update-kb3022345-causing-corrupt-files/

 

not the nsa.... but the kgb

 

wont start in safe mode either, keeps on booting into the windows repair

i have been reading some of that, but those solutions seem to be tailored to people who can still boot into windows

[KillJoy]

Offload your User Data, Wipe and Reload.

 

 

KillJoy

[Exodus]

Offload your User Data, Wipe and Reload.

 

 

KillJoy

 

Yup.

[russian rocket]

Offload your User Data, Wipe and Reload.

 

 

KillJoy

 

fuck...i hate doing that. such a pain in the ass, you think thats really my only option here?

[Exodus]

One thing I love about windows 8.1 is the ability to restore the OS and keep all my files intact.

[unfunnyryan]

I'd check that hard drive for errors...hashes going wrong doesn't just happen if nothing changes.

[Coaster]

fuck...i hate doing that. such a pain in the ass, you think thats really my only option here?

 

I've been doing this a long time. You could spend 20 hours working on it and not fix it or 3 - 4 re-installing. If I can't fix it in about an hour it gets nuked.

[russian rocket]

dammit... well thanks for your guys' help, im gonna spend another hour on it and then probably transfer my shit off it...

[jeffro]

One thing I love about windows 8.1 is the ability to restore the OS and keep all my files intact.

 

You can do this with windows vista and 7 assuming you make regular backup images using the built in backup utility. You could try some of the Hirens Boot CD utilities. Doubt any of them will fix your errors though.

 

As above, pull the files off, reinstall windows, enjoy your fresh machine.

[87GT]

How old is the hard drive? It could be physically going bad. I suggest you scan for bad sectors before you reinstall windows. You can do this in DOS with Hiren's boot CD. If you have a working PC with a CD Burner it is really easy to make. PM me if you need a copy.

 

Edit: You could also make a bootable USB stick if your motherboard supports booting from USB. It probably does.

[Casper]

Stop using Windows.