Registry Anomaly

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 70
    Win 7 64 bit Home Premium
    Thread Starter
       #21

    JoWazzoo said:
    You will need to use some "substring ** commands to dig out the errors in the CBS.log" as that file is HUGE. And then good luck. It can be a pain to isolate the files and find replacements as uncorrected errors are due to the backups being hosed as well.

    Anything touched by SFC will have a [SR] in the entry, but they will be far too many of these in the CBS file. And CBS has a ton of other crap in them.

    How do I analyze the command to detect corrupt files in Windows 7? - Super User

    Search for:

    "corrup"
    "repair"
    "Repairing corrupted file"
    "Cannot repair member file"
    "Repaired file"

    Easiest to do this in a command prompt and log in to the directory that includes. CBS.log

    then you can use something like

    findstr /c:"Cannot repair" CBS.log | More

    Or redirect the output to a text file

    > sfcdetails.txt

    instead of piping thru More
    As I noted earlier: When I try to open the CBC.log file, access is denied!!

    I opened the command prompt as Admin. before generating the SFC logfile. The CBS.log file is 1.58mb and permissions are read/write for Admin.

    Do I have to generate the logfile in SAFE mode? If so, this brings up another problem: I CAN NO LONGER CALL UP THE ADVANCED BOOT OPTIONS MENU BY HOLDING F6!!!!

    Do I have to boot into command prompt using a boot disk?

    HEEEEEELLLLLPPPPPP!!!!!.............this started out as 1 problem and has grown to 3.
    Attached Thumbnails Attached Thumbnails Registry Anomaly-1.jpg  
      My Computer


  2. Posts : 57
    Windows 7 Pro 64
       #22

    You must need to change Permissions - not sure on that one. That doesn't make sense.

    And yes one to three is typical when a machine is hosed.

    Are you sure F6 is the correct one for your machine? What IS your machine?

    Do you have a System Repair disk?

    And yes - Safe mode would be best at this point.
      My Computer


  3. Posts : 57
    Windows 7 Pro 64
       #23

    @Snick - whatever your link is sposed to be it is wrong. System Update Redness Tool
      My Computer


  4. Posts : 57
    Windows 7 Pro 64
       #24

    Joe - please try to keep posts in one thread. Please.

    Are you pressing it every second or so after turning on the machine?
      My Computer


  5. Posts : 3,615
    Win 10 x64, Linux Lite, Win 7 x64, BlackArch, & Kali
       #25

    I corrected my link error in prior post(s) Try this link, think my copy & paste didn't work for link System Update Redness Tool x64

    If you download and run SURT it will create a temporary file located at: C:\Windows\Logs\CBS\ with a section that indicates missing or corrupt files (easier to read) I should have the missing cats, mums, or manifests in my repository 400,000+ files.
      My Computer


  6. Posts : 70
    Win 7 64 bit Home Premium
    Thread Starter
       #26

    JoWazzoo said:
    Joe - please try to keep posts in one thread. Please.

    Are you pressing it every second or so after turning on the machine?
    I didn't want to further complicate an already complicated thread, but better this way, for me anyway.

    Tried continuous press, press very quickly, and press every second or so.

    It always worked before, no matter what pressing frequency I used.

    Replaced keyboard last month. Tested just before with an online keyboard tester and ALL keys work, including F8. Also, F12 (boot options) works as well.
      My Computer


  7. Posts : 70
    Win 7 64 bit Home Premium
    Thread Starter
       #27

    Snick said:
    Try this link, think my copy paste didn't work for link System Update Redness Tool x64
    Yes.............already got around the typo.

    I added a program to short-circuit the automatic Win 10 upgrade. Will playing with the update manager get me back into those annoying (and resource killing) update downloads.

    I shut off auto update and do my own every couple weeks.
      My Computer


  8. Posts : 70
    Win 7 64 bit Home Premium
    Thread Starter
       #28

    JoWazzoo said:
    You must need to change Permissions - not sure on that one. That doesn't make sense.

    And yes one to three is typical when a machine is hosed.

    Are you sure F6 is the correct one for your machine? What IS your machine?

    Do you have a System Repair disk?

    And yes - Safe mode would be best at this point.
    Admin (ME) has full read/write permissions already.

    Yes, it has always been F8.

    Home built by me. AMD dual core x64 bit
    16 Gb ram
    SSD primary 210gb, HDD secondary Seagate Barracuda 1tb

    Windows 7 x64 / UBUNTU dual boot
    Gigabyte mainboard
      My Computer


  9. Posts : 3,615
    Win 10 x64, Linux Lite, Win 7 x64, BlackArch, & Kali
       #29

    SystemUpdateReadinessTool creates its own temporary log at: C:\Windows\Logs\CBS\CheckSUR is much easier to read and will open in Notepad.
      My Computer


  10. Posts : 70
    Win 7 64 bit Home Premium
    Thread Starter
       #30

    Snick said:
    SystemUpdateReadinessTool creates its own temporary log at: C:\Windows\Logs\CBS\CheckSUR is much easier to read and will open in Notepad.
    Great.

    There are 2 logs generated at that location:

    CheckSUR,log
    and
    CheckSURpersist.log

    should I attach both?
      My Computer


 
Page 3 of 6 FirstFirst 12345 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:16.
Find Us