Windows 8.0 x64; Image Version: 6.2.9200.16384; Corruption; Please help

[Steveg722]

Windows 8.0 x64; Image Version: 6.2.9200.16384; Corruption; Please help

2:18 PM 1/27/2022

Hi,

Thinking of upgrading to Win8.1 but before doing so, would like to clean up Win8.0 so I can save a good Win8.0 IMAGE before upgrading to Win8.1.

A few weeks ago I chased down "who was niemiro" and found Sysnative.com/forums; Amazing to see how much your people like & enjoy (& are expert at) helping people solve Windows Puzzles. Given that and my limited knowledge re this, decided it was past time to seek your help.


SYMPTOMS [C:\Windows\Logs\CBS];
>Since ~May2019, content of copies of CBS.log have had many suspicious entries (eg, Failed to delete extra backup log files AND Failed to delete oldest backup log. [HRESULT = 0x80070005 - E_ACCESSDENIED]);
>In Aug21, I took the then current CBS.log file "out of service" which forced Windows to create a new one but that did not seem to solve anything.
>Last CbsPersist*.log file still shows 8:00 PM 5/23/2019; 15955KB; Seems not-normal?
SYMPTOMS; [SFCfix.exe];
>Have only run this a couple times recently; Last try results=No corruptions have been detected on this computer.
SYMPTOMS [sfc /scannow];
>Consistent Result for several years=Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log; [CBS.log has not been showing any Details]
SYMPTOMS [DISM.exe /Online /Cleanup-image /Restorehealth];
>Most recent result=Error: 0x800f0906 The source files could not be downloaded.; I have tried re-running with /Source option but sources I have tried have not solved the problem and I really don't have any idea how to find and use an appropriate "source".

>PLAN TO UPLOAD 4 FILES (See below)


Would greatly appreciate any help you can give me;


Thanks,
BeWell,
Steveg722

220127_1735; ADDED NEW UPLOAD=220127_1700;Win_LOGS_CBS.zip after reviewing Windows Update Forum Posting Instructions


PLAN TO UPLOAD; ADDED
M:\15r;WinBACKUP;201115_1042\ROBOCOPIESfr15r
220127_1700;Win_LOGS_CBS.zip
5:33 PM 1/27/2022; 19476KB

PLAN TO UPLOAD (This file has detailed info re my efforts to fix this from 25Jan[top]-27Jan2021[bottom])
Sysnative_com_forums;Post1;220127_0745.txt


PLAN TO UPLOAD
C:\Windows\Logs\CBS
CBS - Copy (45).log
5:41 AM 1/27/2022; 2408KB

PLAN TO UPLOAD
C:\Windows
WindowsUpdate - Copy (24).log
5:53 AM 1/27/2022; 1519KB

PLAN TO UPLOAD
C:\Windows\Logs\DISM
dism - Copy (31).log
8:48 AM 1/27/2022; 20226KB


REF INFO ONLY
C:\Windows\Logs\CBS
CBS;OUT;210812_0715.log
6:21 AM 8/22/2021;

REF INFO ONLY
C:\Windows\Logs\CBS
CbsPersist_20190524005835.log
8:00 PM 5/23/2019; 15955KB

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 

[Steveg722]

7:54 AM 1/28/2022
REPLYING TO UPLOAD 2 FILES THAT GOT LOST ON PRIOR POST

UPLOADING
M:\15r;WinBACKUP;201115_1042\ROBOCOPIESfr15r
220127_1700;Win_LOGS_CBS.zip
5:33 PM 1/27/2022; 19476KB

UPLOADING
C:\Windows\Logs\CBS
CBS - Copy (45).log
5:41 AM 1/27/2022; 2408KB

 

[Steveg722]

12:08 PM 1/28/2022 EST

PRIOR POST (Today at 7:56 AM) DOES NOT SHOW THE 3 FILES I HAD ATTACHED (& APPEARED TO UPLOAD BUT THE IMAGE ABOVE THE FILENAME NEVER CAME) BEFORE I CLICKED "POST REPLY"????

220127_1700;Win_LOGS_CBS.zip
CBS - Copy (45).log
Sysnative_com_forums;Post1;220128_0754-220127_0745.txt

I HAVE NO IDEA WHY THOSE UPLOADS FAILED BUT TO GET MY DATA AVAILABLE TO YOU, I PUT ALL MY 6 FILES

C:\Windows\Logs\CBS
1>CBS - Copy (45).log
5:41 AM 1/27/2022; 2408KB

C:\Windows
2>WindowsUpdate - Copy (24).log
5:53 AM 1/27/2022; 1519KB

C:\Windows\Logs\DISM
3>dism - Copy (31).log
8:48 AM 1/27/2022; 20226KB

M:\15r;WinBACKUP;201115_1042\ROBOCOPIESfr15r
4>220127_1700;Win_LOGS_CBS.zip
5:33 PM 1/27/2022; 19476KB

C:\Windows\Logs\CBS
5>CBS - Copy (45).log
5:41 AM 1/27/2022; 2408KB

M:\15r;WinBACKUP;201115_1042\15r;MAINT
6>Sysnative_com_forums;Post1;220128_0754-220127_0745.txt
8:12 AM 1/28/2022; 18KB


INTO A FOLDER NAMED
220128_0812;UploadTo;sysnative.com

I THEN UPLOADED & SHARED THAT FOLDER ON GOOGLE DRIVE AT LINK=

220128_0812;UploadTo;sysnative.com - Google Drive
220128_0812;UploadTo;sysnative.com

APOLOGIZE FOR ANY INCONVENIENCE AND LOOK FORWARD TO SOME HELP.

Thanks,
Steveg722

 

[PeterJ]

Hello and welcome,

Please do following only.

1. Open an elevated command prompt.
2. Copy and paste the following commands into it, press enter after each.
   

   sfc /scannow

3. 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. Zip this file and attach the zipped cbs.txt to your next post.

 

[Steveg722]

220202_2315 EDT

Greetings PeterJ

Thanks for the welcome & offering to help me with my problem....

>CMD_ADMIN; sfc /scannow;
Windows Resource Protection found corrupt files but was unable to fix some
of 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.
>Zipped the CBS.txt file on the desktop.
>Attached=CBS.zip

Steve

 

[PeterJ]

Open the file explorer and browse to the folder C:\Windows\Logs\CBS.
Take a screenshot of the file explorer window. Read this on how to take a screenshot.
Upload the image file to a file-sharing site such as imgur.com and post the downloadlink.

 

[Steveg722]

220203_1255 EST

Hello PeterJ

>file explorer; C:\Windows\Logs\CBS
>Screenshot; pasted to paint.exe; SavedAs=15r;WinExp;Windows_LOGS_CBS;220203_1230.png
>Uploaded to GoogleDrive; SharedLINK=
15r;WinExp;Windows_LOGS_CBS;220203_1230.png

Hoping you can access it there.

Curious to know if you were aware of the folder/files I previously (Post#3) uploaded to GoogleDrive; Shared Link=
220128_0812;UploadTo;sysnative.com - Google Drive

If not, suggest you check them out as it seems they may be helpful to your efforts to help me.


Thanks,
Steve

 

[PeterJ]

Step 1:
Open an elevated commandprompt.
Copy and paste the following commands into it, press enter after each.

cd c:\windows\logs\cbs

Wait for this to finish before you continue.

attrib -r /s *.log

Close the commandprompt window.

Step 2:
Open the file explorer and browse to the folder C:\Windows\Logs\CBS.
Take a screenshot of the file explorer window again.
Upload the image file to a file-sharing site such as imgur.com and post the downloadlink.

 

[Steveg722]

220203_2028 EST

CMD_ADMIN
>cd c:\windows\logs\cbs
>attrib -r /s *.log

>Screenshot; pasted to paint.exe; SavedAs=15r;WinExp;Windows_LOGS_CBS;220203_2018.png
>Uploaded to GoogleDrive; SharedLINK=
15r;WinExp;Windows_LOGS_CBS;220203_2018.png

Hope you can access it;

Any chance you could share any of your thoughts re RootCause would be helpful...

Thanks
Steve

 

[PeterJ]

Any chance you could share any of your thoughts re RootCause would be helpful...

For some reason the read-only file attribute on all .log files in the folder C:\Windows\Logs\CBS was set. We removed that.
Please do following only:

1. Open an elevated command prompt.
2. Copy and paste the following commands into it, press enter after each.
   

   sfc /scannow

3. 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. Zip this file and attach the zipped cbs.txt to your next post.

 

[Steveg722]

3:00 PM 2/4/2022 EST

Hi again PeterJ


Before proceeding, we need to come to agreement re the file attributes of files in the C:\Windows\Logs\CBS folder prior to my running the (attrib -r /s *.log) yesterday evening as reported in Post#9.

Please take a look at contents (64 files) in the 220127_1700;Win_LOGS_CBS.zip file in the 220128_0812;UploadTo;sysnative.com folder I uploaded to GoogleDrive (Link= 220128_0812;UploadTo;sysnative.com - Google Drive) and mentioned in Post#3

From what I see, the read-only file attribute on the (active) C:\Windows\Logs\CBS\CBS.log file (& all five (5) CbsPersist_*.log files) was NOT (& to my knowledge has never has been) set.
Only the "- Copy*.log" files have the read-only attribute set (I did that to preserve content).

Please confirm for me we agree we have no evidence the (active) C:\Windows\Logs\CBS\CBS.log file has ever been set to read-only on my 15r PC (If you do not agree, please fill me in).


Now for the results you requested
>sfc /scannow

2:32 PM 2/4/2022
CMD_ADMIN
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DATE
The current date is: Fri 02/04/2022
Enter the new date: (mm-dd-yy)

C:\Windows\system32>TIME
The current time is: 14:11:32.54
Enter the new time:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of 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.

2:35 PM 2/4/2022
C:\Windows\system32>

C:\Windows\system32>copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
1 file(s) copied.

C:\Windows\system32>

>I renamed that cbs.txt file as cbs;cbs;15r;220204_1435.txt and Zipped and uploaded it as 15r;220204_1435.zip
(The .zip file would not upload using Attach files???; trying the .txt version; also would not upload here; will put .txt version on GoogleDrive; LINK= cbs;15r;220204_1435.txt)

Thanks,
Steve

 

[PeterJ]

First of all, best not to modify the contents of the system folder C:\Windows\Logs\CBS manually.
If you need backups of those files, copy them to another folder, for example C:\mybackup\cbslogs

From what I see, the read-only file attribute on the (active) C:\Windows\Logs\CBS\CBS.log file (& all five (5) CbsPersist_*.log files) was NOT (& to my knowledge has never has been) set.
Only the "- Copy*.log" files have the read-only attribute set (I did that to preserve content).

The file CBS - Copy (34);AfterSFCscannow.log has not the read-only attribute set.

Please confirm for me we agree we have no evidence the (active) C:\Windows\Logs\CBS\CBS.log file has ever been set to read-only on my 15r PC (If you do not agree, please fill me in).

I cannot say that. The read-only attribute may have been reset at some time.

All that said now the file cbs.log reveals the issues that were found.
Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

 

[Steveg722]

220207_1210 EST


Good Day PeterJ,

Happy Monday

Over the weekend, as the one responsible for this 15r PC [do no harm, understand RootCause(s), & be able to easily UNDO any changes] , spent some time thinking about all this and doing some more investigating....

1) After digesting your Post#12 of 220204_1820, realized I had no idea exactly what running SFCfix with the SFCfix.zip file I downloaded from Post#12 would do to my 15r PC. All you mentioned was "...the file cbs.log reveals the issues that were found. Follow the instructions below please." Understand you were referring to the cbs;15r;220204_1435.txt file I had uploaded to GoogleDrive as described in Post#11.

1a) My exam of that SFCfix.zip file suggests it includes the following five (5) files (Each with a specific PATH):
task manager.lnk
performance monitor.lnk
resource monitor.lnk
desktop connection.lnk
windows journal.lnk
wordpad.lnk

1b) My exam of the >dism - Copy (31).log file I uploaded prior (see Post#3), shows 2022-01-25 13:09:23, Info; Checking System Update Readiness.; Total Detected Corruption: 22;

1c) As of this writing, I found I do now have one (1) "recent RP" showing in SYSTEM RESTORE; NEWEST=220130_065646; so if it doesn't get overwritten, I could, hopefully, use that RP to "UNDO" whatever running SFCfix with that SFCfix.zip might do (if I "had to").

1d) Me being me, before making any changes, I decided to understand the (5) Vs (22) difference so went off and took a look at what those (22) items are Vs what the (5) files that are in that SFCfix.zip file;

1e) Please consider the following PivotTable1Summary of my findings; Turned out, the (5) files&paths do appear in the (22) "corrupt items" per DISM.





1f) Used WINEXP to search 15r;C:\Windows for each of the (5) files found in the SFCfix.zip file; Interestingly, while the >dism - Copy (31).log only lists each of those (5) files (with one specfic path) "as corrupt", my WINEXP searches found the following #instances of each file:

FILE #INSTANCESunderWindows (>1 due to different PATHs) INSTANCEfoundinSFCfix.zip
task manager.lnk 5 (as Task Manager; 3=1,214bytes; 2=1,021bytes) 1,120bytes
performance monitor.lnk 1 (as Performance Monitor; 1,198bytes) 1,104bytes
resource monitor.lnk 3 (as Resource Monitor; 1,202bytes) 1,108bytes
desktop connection.lnk 5 (as Remote Desktop Connection; 1,305bytes) 1,215bytes
windows journal.lnk 3 (as Windows Journal; 1,282bytes) 1,156bytes
wordpad.lnk 3 (as Wordpad; 1,288bytes) 1,154bytes


At this point, please help me by responding to these questions?
Q1) Do the PivotTableSummary contents/conclusions make sense to you? If not, why not?

Q2) IF so, how does one explain the WINEXP search 15r;C:\Windows results (where "same file" exists under different PATHs)? Why would DISM only report one (1) of them (filename + PATH) as "corrupt"?

Q3) IF I were to run SFCfix with the SFCfix.zip file from Post#12, what steps would it execute (for example, re task manager.lnk)? Would the SFCfix.txt file you mentioned in Post#12 be a detailed log documenting each step?

Q4) IF SFCfix.zip file from Post#12 is only designed to "deal with" the (5) FILEs listed under 1a), what are your thoughts about the other (17) files reported by DISM as "corrupt"?


Q5) When DISM reports a file as "corrupt", what are the various reasons DISM can ID it as "corrupt"?



Thanks,
Steve

 

[PeterJ]

As I said in message #12 there are some files corrupt. For now that are the 6 .lnk files you mentioned.
Please perform the instructions in message #12 to replace them and provide the requested result.

 

[Steveg722]

220207_2128 EST


PER Post#13; 1c) As of this writing, I found I do now have one (1) "recent RP" showing in SYSTEM RESTORE; NEWEST=220130_065646;

QUESTION; IF I run SFCfix.exe with the SFCfix.zip file as you proposed in Post#12 any chance it could cause me to lose SYSTEM RESTORE RP NEWEST=220130_065646?

I await your answer please.

Thanks

 

[PeterJ]

QUESTION; IF I run SFCfix.exe with the SFCfix.zip file as you proposed in Post#12 any chance it could cause me to lose SYSTEM RESTORE RP NEWEST=220130_065646?

No. The fix will replace the 6 .lnk files only.

 

[Steveg722]

2:00 PM 2/8/2022 EST


Greetings PeterJ

>Just ran the SFCfix.exe/SFCfix.zip job you proposed in Post#12; You should find the resulting SFCfix.txt file ATTACHED to this Post as SFCFix.txt.

>Noticed in my Post#14, I mis-stated the # of files I found in your SFCfix.zip file; Making the following CORRECTIONs here re my Post#14; Sorry.

1a) My exam of that SFCfix.zip file suggests it includes the following SIX (6) [NOT 5] files (Each with a specific PATH):

1d) Me being me, before making any changes, I decided to understand the (6) [NOT (5)] Vs (22) difference so went off and took a look at what those
(22) items are Vs what the (6) [NOT (5)] files that are in that SFCfix.zip file;

1e) Please consider the following PivotTable1Summary of my findings; Turned out, the (6) [NOT (5)] files&paths do appear in the (22) "corrupt items" per DISM.

1f) Used WINEXP to search 15r;C:\Windows for each of the (6) [NOT (5)] files found in the SFCfix.zip file; Interestingly, while the >dism - Copy (31).log only lists each of those (6) [NOT (5)] files (with one specfic path) "as corrupt", my WINEXP searches found the following #instances of each file:

Q4) IF SFCfix.zip file from Post#12 is only designed to "deal with" the (6) [NOT (5)] FILEs listed under 1a), what are your thoughts about the other (16) [NOT (17)] files reported by DISM as "corrupt"?


Please share your thoughts/proposed steps to help me fix the remaining "corrupt" files?


Thanks,
Steve

 

[PeterJ]

Please share your thoughts/proposed steps to help me fix the remaining "corrupt" files?

Restart the computer.
Open an elevated command prompt.
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"

This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.

 

[Steveg722]

9:20 PM 2/8/2022

PeterJ

>Assignment accomplished; ReBooted; CMD_ADMIH; Ran sfc /scannnow;

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.

>NO CBS.txt found on DESKTOP; Instead, ATTACHED pls find CBS - Copy (50)AfterSFCscannow.log as CBS.log (As found AFTER sfx /scannow; Did not bother zipping it).


Your feedback/conclusions/suggestions please?

Thanks
Steve

 

[Steveg722]

8:08 AM 2/9/2022
NEW Post#20


Good morning PeterJ

A bit more info re current 15r status:

>220209_0747;DISM;The component store is repairable.; The operation completed successfully.; 220209_0718;NEWDAY;CMD_ADMIN;Dism /Online /Cleanup-Image /ScanHealth;GO

>>220209_0800;EVENTVWR;SETUP;NEWEST;Source: Microsoft-Windows-Servicing; Date: 2/9/2022 7:46:28 AM; Event ID: 1015; 0 of 16 instances of system store corruption have been repaired.


So, from Post#17,
Q4) ......., what are your thoughts about the other (16) [NOT (17)] files reported by DISM as "corrupt"?


Look forward to your feedback/conclusions/suggestions please?


Thanks
Steve