[SOLVED] [8.1Upd3 x86] SFC errors on "windows Journal.lnk".

D

dave jackson

Member
Joined
Dec 13, 2017
Posts
8
I have identical issue as another post in this forum, but did not want to use script file provided as the warning advised not to.

I have run sfc /scannow several times (rebooting between each). I have rebuilt repository with DISM from the original 8.1 install DVD. Finally running the SFCfix several times not no avail. The result always being:

CORRUPT: C:\WINDOWS\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\Windows Journal.lnk

I am not even sure I should be concerned as I would never use tablepc-journal.exe, but am concerned with error. I am attaching output from SFCfix, and the compression CBS logs
 

Attachments

Re: SFC errors on "windows Journal.lnk". Win8.1

Hello and welcome to Sysnative!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

SFCFix.txt
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-12-28 10:35:26.611
Microsoft Windows 8.1 Update 3 - x86
Using .zip script file at C:\Users\dave jackson\Desktop\SFCFix.zip [0]
 

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\windows journal.lnk
Successfully copied file C:\Users\dave jackson\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\windows journal.lnk to C:\WINDOWS\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\windows journal.lnk.
Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\windows journal.lnk
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.3.9600.18295_none_ac474dc0c0393686\windows journal.lnk
PowerCopy:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-12-28 10:35:29.052
Script hash: wxbHdotWPMsFBhqt5pfme6KpgNQOmQKG9cmrX/9t6QA=
----------------------EOF-----------------------
 
C:\WINDOWS\system32>copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
The syntax of the command is incorrect.

looked fine to me but manually copied file. I had to zip it to attach as was too large
 

Attachments

windows Journal.lnk corruption now appears permanently fixed..thank you. However, sfc /scannow repeatedly (tried 3 more times) terminates with following


Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

The file allows detected as corrupt, and sfc says it fixed it is C:\WINDOWS\System32\invagent.dll. Do I need to be concerned? I attached zipped cbs.log (cbstxt.zip)
 

Attachments

Remove Update Manually
 1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter
wusa /uninstall /KB:2976978

4. Let me know if it says it was successful or if there are any errors.
 
ran sfc /scannow twice .................both times only corrupt file was invagent.dll BUT the second run returned

Beginning system scan. This process will take some time.Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top