System Info And System Logs

Discussion in 'Software' started by AndyDK, Mar 5, 2016.

  1. AndyDK

    AndyDK Private E-2

    Hi, I've had some problems with my PC and someone has asked me on a forum to upload my System Info and System Log and make it accessible to anyone, and I was also thinking of uploading the Log file generated by SFC. Now this questions answer may seem obvious to someone in the know, but unfortunately I'm not, so please bear with me. Is any info exported in these files dodgy in the wrong hands. Will any of these files contain user account passwords or the Windows 7 product key etc, as by the sounds of it they contain a record of what the system is up to.
     
  2. _nullptr

    _nullptr Major Geeky Geek Geek

    If you're referring to Windows System Information application, the report generated contains no passwords, product keys or anything of a sensitive nature. The same goes for the CBS.log generated by SFC.
    What problems are you having with your PC?
     
    satrow likes this.
  3. AndyDK

    AndyDK Private E-2

    This is a shortened version of what I was asked to do "Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Please upload and share with everyone a fresh copy of your System log from your Event Viewer.To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System." So definitely nothing sensitive there just to double check?.

    The problem is with the upgrade KB3121416. It installs, but SFC then reports corruption. SFC /SCANNOW claims to have fixed that corruption, but another scan proves it is still there. Here is an excerpt from CBS.LOG
    "2016-03-05 11:21:34, Info CSI 0000068c [SR] Verify complete
    2016-03-05 11:21:34, Info CSI 0000068d [SR] Repairing 2 components
    2016-03-05 11:21:34, Info CSI 0000068e [SR] Beginning Verify and Repair transaction
    2016-03-05 11:21:34, Info CSI 0000068f Hashes for file member \??\C:\Windows\system32\wbem\aeinv.mof do not match actual file [l:18{9}]"aeinv.mof" :
    Found: {l:32 b:mRMm+zUZy7MLGo62gOiBRfsAPmZ1LpbDEpQrOuG22xc=} Expected: {l:32 b:CbYTVun9lFxGOENTdB1DSPaabSP/6/hoGlfxvZcH2Ic=}
    2016-03-05 11:21:34, Info CSI 00000690 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:18{9}]"aeinv.mof" from store
    2016-03-05 11:21:34, Info CSI 00000691 WARNING: File [l:18{9}]"aeinv.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership
    Old: Microsoft-Windows-Application-Experience-Inventory, Version = 6.1.7601.18783, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.1.7601.19105, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    2016-03-05 11:21:34, Info CSI 00000692 Hashes for file member \??\C:\Windows\system32\wbem\aeinv.mof do not match actual file [l:18{9}]"aeinv.mof" :
    Found: {l:32 b:CbYTVun9lFxGOENTdB1DSPaabSP/6/hoGlfxvZcH2Ic=} Expected: {l:32 b:mRMm+zUZy7MLGo62gOiBRfsAPmZ1LpbDEpQrOuG22xc=}
    2016-03-05 11:21:34, Info CSI 00000693 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:18{9}]"aeinv.mof" from store
    2016-03-05 11:21:35, Info CSI 00000694 WARNING: File [l:18{9}]"aeinv.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership"
     
  4. _nullptr

    _nullptr Major Geeky Geek Geek

    No, definitely nothing sensitive.
     
  5. AndyDK

    AndyDK Private E-2

    Thanks
     
  6. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    Easy solution, don't install KB3121416.
    http://www.eightforums.com/windows-...465-file-corruption-latest-batch-updates.html

    I had a similar situation in Win 7. I never installed an update that was causing sfc /scannow to report a problem. I've hidden the update so I would not accidentally install it.

    Just went back over my notes. The update KB3022345 issued in August 2015 generated false problems when sfc was run in Win 7.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds