Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by nunitak

  1. All questions now moot as I've done a full Windows 7 Pro 32 install and re-installed all of my applications software, created Repair, Boot and PW Recover Disks plus Boot USB Stick. However this thread is useful for anyone who needs to replace a corrupt file. I'll have a full image Acronis Backup too, so it won't matter if Hard Drive croaks again, but it is brand new. This should give me full coverage insurance against everything except nuclear bulls eye here.
  2. Well, not all of us have deep pockets for the latest spiffy pc, albeit I can build one cheaply that is better than my Dell Latitude D830 Laptop on which I just now finished doing a Full Install and Full Update of Windows 7 Pro 32 bit. As I do not do this stuff everyday, being mostly a cosmic life sciences person, it took me two failing tries over day and a half, and then one full attentions focused success, somewhat of a miracle too for a 70 year old. Now I can continue my writing and blogging in STYLE. I did a Hangman Game for typing students once on the TI-99/4A. Hmmm. Circa 1984 or 1985 I think... You can see some of those nifty TI-99/4As for sale really cheap on Ebay (eBAY ?). My Sinclair ZX81 got lost in SLC, Utah. Youngsters probably have no clue about that one. I never play games and cannot see fast moves nowadays. Any ol' cheapie with XP or better is good enough, Win 7 Pro has been a rather impressive splurge. I like it! BEST SUGGESTION: Make SURE it is working and give to a brainy and very poor student age 11 to 21 When I left Michigan in 2011 the starving unemployed were grabbing all old appliances, computers, whatnot, working or not. I don't know where the loaded pick-up trucks went, but apparently someone was paying a little, maybe a computer salvage and restore guy, many such shops were around there, and many go overseas for my same suggestion as here. Help those students! !
  3. I don't recall anything from command prompt except sort of like "this will take some time" at the beginning, maybe a percent completed value while running. and at the end it refers to CBS.log saying to look at that for details. Ran it once in Vista and once in Win 7 Pro and it said some files could not be fixed -- talking about Autochk -- but it did not say that on the LAST run which created the evidentiary CBS Log showing in boxes here following your "curiousity killed cat" box. The last run didn't say corrupt Autochk because I fixed Autochk by replacing it. I know it works because it does both Chkdsk /f and /r The computer villeins out there sometimes manage to STICK something on my computer which antivruses et cetera cannot remove (and sometimes don't even notice) but I uninstall infected applications software or restore selected items from Acronis Full Image backup(s). So far nothing has exceeded my techniques, especially a Full Image Restore (all Source BackUps made when computer is optimized every which way and in perfect order). It seems to me the miscreants are more numerous and aggressive with various malware and tricks, especially during last 13 years. But they focus on Shoppers, Game Players, Movie Downloaders and MP3 sites for Popular music, screensaver downloads -- all stuff I never do, plus I can tell from experience which to stay away from, and I have McAfee Site Advisor too. I think Autochk got messed up when computer had Vista and the old HDD was croaking. I put Vista backup on new HDD, had Autochk troubles, upgraded, still had trouble (only with that). Fixed now, thank you again for the help. If you have any Q in my areas, I owe you... And I am helpful too. My wordpress stuff is free, but only the intelligent and non-lazy read it -- clicking items there maximizes the result and likewise for Yahoo Answers. If you think I was allowed to go through college for several degrees, you are wrong. I was never allowed to go through college. But heavenly justice is nearing, no problem...
  4. End of CBS Log: It says "Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired." That is ALL it says, zero instances of "integrity" word other than 2 instances (alone) shown in previous post. If it said "integrity violations" it would have to use some other words than "integrity" and "violation" AND further, the word "integrity" and the word "violation" are not found anywhere, neither singular nor plural for the latter. Likewise for "error" and "errors" -- zero occurrences of either word in CBS Log. Is it very difficult to believe a bear could have a spiffy computer? I am always working to keep it clean, more so when visiting snoopy nations or when I notice something is slightly flaky or worse. Do you ask because something else is amiss in your opinion? From CBS Log? I don't think I am the only person with occasional problems down here, and you would be very surprised what else I know, even for many, many, many light years distance, and timewise for that matter, both future and past... Knowledge is good at a particular time and place, but wisdom is good anywhere throughout eternity. Visit http://nunitak.wordpress.com or Ursus Particularies on Yahoo Answers
  5. The word "integrity" is mentioned only twice in CBS Log, and that occurs in the 1st 7th of the log, near the bottom of the 1st 7th: 2014-01-08 02:02:22, Info CSI 0000005d Repair results created: POQ 17 starts: [iT IS NEAR THE BOTTOM OF THIS CBS LOG SELECTED PORTION] 0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\f4b3dc923f0ccf014807000084014405._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms" 1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\f4b3dc923f0ccf014907000084014405.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms" 2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\d59ae8923f0ccf014a07000084014405.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms" 3: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\5620f2923f0ccf014b07000084014405.$$_system32_bg-bg_3ce955ba8d69a9ab.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_bg-bg_3ce955ba8d69a9ab.cdf-ms" 4: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\17e3f6923f0ccf014c07000084014405.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms" 5: Move File: Source = [l:238{119}]"\SystemRoot\WinSxS\Temp\PendingRenames\7744f9923f0ccf014d07000084014405.program_files_dvd_maker_405775de8763ce75.cdf-ms", Destination = [l:150{75}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_405775de8763ce75.cdf-ms" 6: Move File: Source = [l:252{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\d7a5fb923f0ccf014e07000084014405.program_files_dvd_maker_shared_a54613779b918be2.cdf-ms", Destination = [l:164{82}]"\SystemRoot\WinSxS\FileMaps\program_files_dvd_maker_shared_a54613779b918be2.cdf-ms" 7: Move File: Source = [l:238{119}]"\SystemRoot\WinSxS\Temp\PendingRenames\d9b00e933f0ccf014f07000084014405.$$_system32_msdtc_trace_f33466dc5bf36670.cdf-ms", Destination = [l:150{75}]"\SystemRoot\WinSxS\FileMaps\$$_system32_msdtc_trace_f33466dc5bf36670.cdf-ms" 8: Move File: Source = [l:226{11 2014-01-08 02:02:22, Info CSI 3}]"\SystemRoot\WinSxS\Temp\PendingRenames\7b5a1f933f0ccf015007000084014405.$$_system32_cs-cz_3ecfefb68a8fc3f6.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_cs-cz_3ecfefb68a8fc3f6.cdf-ms" 9: Move File: Source = [l:222{111}]"\SystemRoot\WinSxS\Temp\PendingRenames\bda22d933f0ccf015107000084014405.$$_system32_com_066545e3d047e7c7.cdf-ms", Destination = [l:134{67}]"\SystemRoot\WinSxS\FileMaps\$$_system32_com_066545e3d047e7c7.cdf-ms" 10: Move File: Source = [l:216{108}]"\SystemRoot\WinSxS\Temp\PendingRenames\dec634933f0ccf015207000084014405.$$_servicing_fc2045b9046cc796.cdf-ms", Destination = [l:128{64}]"\SystemRoot\WinSxS\FileMaps\$$_servicing_fc2045b9046cc796.cdf-ms" 11: Move File: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\3e2837933f0ccf015307000084014405.$$_servicing_editions_596ea20ddafb9f7d.cdf-ms", Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_servicing_editions_596ea20ddafb9f7d.cdf-ms" 12: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\40334a933f0ccf015407000084014405.$$_system32_ar-sa_3b02d130904371b4.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_ar-sa_3b02d130904371b4.cdf-ms" 13: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\454970933f0ccf015507000084014405.$$_system32_el-gr_429cd0b684dc71bd.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_el-gr_429cd0b684dc71bd.cdf-ms" 14: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\a9c098933f0ccf015607000084014405.$$_system32_da-dk_40b64d5e87b63595.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_da-dk_40b64d5e87b63595.cdf-ms" 15: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\6c8eb0933f0ccf015707000084014405.$$_system32_codeintegrity_e9af9308cfc26dc2.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_codeintegrity_e9af9308cfc26dc2.cdf-ms" No other occurence of the word "integrity" in this document.
  6. Yes, I did sfc /scannow and much else. It repaired a lot and seemed to say at conclusion that it had fixed all found, albeit the exact nature of the fixes is beyond me. No comprende CBS Log I'm afraid. Too much strain on bear heads. Looked like a lot of moving things about, IDK... Next time I install a new system, I will do Full Install from scratch, NOT an Update. Live and learn. Maybe I'll do that with new Win 7 Pro disk later this year, but I am under the gun with work in progress right now, and pc is good-to-go for the time being, until some slack time for scratch install comes up.
  7. Thank you kindly for last given info. Can't try it until done with big project completion, already late, But will be finished with project before January 12, then I'll be able to CONCENTRATE on fixing this durn problem of corrupt Autochk.exe. Your instructions seem clear enough in comparison to opaque and I am usually successful with slightly to medium opaque.
  8. Number 3 is EXACTLY what I want to know: How do I extract ONLY the Autochk.exe file from there. I already know how to take ownership of the corrupt file and replace it [ http://support.microsoft.com/kb/929833 ] but I can do THAT If and only if I have a non-corrupted Autochk.exe file. How do I get the uncorrupted one off my brand new Win 7 Pro full installation or Upgrade Disk?
  9. Scannow result from My CBS Log: (it said "some corrupt files could not be fixed") Scroll to RED below please (2 places) What can I do to get hash check valid Autochk.exe file? I have full Win 7 Pro 32 installation disk, but don't know how to get Autochk.exe out of it and onto my HDD 2013-12-31 12:51:21, Info CBS Starting TrustedInstaller initialization. 2013-12-31 12:51:21, Info CBS Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cbscore.dll 2013-12-31 12:51:22, Info CSI 00000001@2013/12/31:17:51:22.758 WcpInitialize (wcp.dll version called (stack @0x62eade79 @0x69b25d7d @0x69b0205a @0x391c99 @0x391236 @0x76ee75a8) 2013-12-31 12:51:22, Info CSI 00000002@2013/12/31:17:51:22.867 WcpInitialize (wcp.dll version called (stack @0x62eade79 blah blah blah Found: {l:32 b:SsjDmtywA39rN0QxHbdeimVw5JbufoVRyYPnxpZHdeI=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=} 2013-12-31 12:59:02, Info CSI 000001cb [sR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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 2013-12-31 12:59:02, Info CSI 000001cc Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_e3fb573520033bfa\autochk.exe do not match actual file [l:22{11}]"autochk.exe" : Found: {l:32 b:SsjDmtywA39rN0QxHbdeimVw5JbufoVRyYPnxpZHdeI=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=} 2013-12-31 12:59:02, Info CSI 000001cd [sR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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 2013-12-31 12:59:02, Info CSI 000001ce [sR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery" 2013-12-31 12:59:02, Info CSI 000001cf Hashes for file member \??\C:\Windows\System32\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  10. I've already done that Xilo. Reason I upgraded Windows Vista Business 32 is mostly due to Chkdsk not working, Autochk reported as corrupt, no entry point for DLL and similar. Reported as cannot fix by sfc /scannow So, now I've upgraded to Windows 7 Pro 32 and I do not understand why corrupt files were not replaced. I am loathe to do a full wipe and reformat and then reinstall Win 7 Pro because I'll lose all the current applications softwares I have -- they will all need reinstallation plus the Win 7 will have to go through all upgrades again, best part of a month more work for me plus delaying all my computer work and blogging. Currently using fsutil repair set c: 1 But I will try it one more time, already wiped software downloads in windows per Code 8024200D and Code 80070003 so that KB2862330 would install successfully. Biology head nearly ready to croak on this.
  11. -- see lower right of attachment: It keeps popping out of there all over lowere right of pc screen every time you are using WiseCleaner.
  12. Wisecare 365 does not fix it Action Center says disk errors present, suggests reboot, but chkdsk does not run on reboot I have installation disk for Win 7 Pro 32 but want to proceed in manner not requiring total disk wipe, reformat, reinstall which would require reloading all softwares. How to do minimal repair of restoring CHKDSK function??? Currently surviving on fsutil repair set c: 1 I am NOT a MSCE nor anything else like that, mostly biology head, but not a pc dummy Operating system:Windows 7 Professional (32 bit) Service Pack 1 System root: C:\Windows Available physical memory: 2038 MB CPU: Intel® Core2 Duo CPU T7500 @ 2.20GHz Drive Info: C: 74.53 GB F: 365.33 GB Internet Explorer: 11.0
  • Create New...