Post problem reports here for Batch files for use in BSOD debugging

When V2 is ran over and over again it always creates a new file on the desktop.
It does not replace the existing file as it has a different date.
Will this then work in the same fashion for tuneup_plus_log.bat?

The issue with SFC_details.txt was that it created a new empty file on the desktop.

I can put "Tuneup.log" and "SFC_details.txt" into a single ZIP file with a timestamp.

The script does not run the second scannow if the first had no problems.
Can the script not create a details.txt if it is blank and report that it did not create it because it was blank?

If you are able to modify it soon I'll test it on this computer before a reboot to see if it still creates an empty run.

zbook said:

Can the script not create a details.txt if it is blank and report that it did not create it because it was blank?

Try the script attached below:

This computer is having a problem with a windows update.

It has crashed twice.

https://support.microsoft.com/en-us/...c-1e80ed9f4a00

It was supposed to block the update per the notice but it didn't and required another startup repair.

The script is running now and this time scannow is running.

The first time it would not let scannow run as an update was pending.

So far it has not found an update to install and there is no prompt to update with restart.

Code:

    Operation (1): SFC.exe is checking the system files.

New titles on the desktop generally appear in the first opening on the left side.

The running of the latest script did not create a new link and replaced an old link.

Also there was no new location for sfc_details.

Please modify so that it works similar to V2 and always creates a new location of the file on the desktop.

Code:

    Started on Sun 09/19/2021 at  1:06:47.91 

        [SFC /ScanNow] 

Beginning system scan.  This process will take some time.

Results: 
 
Windows Resource Protection found corrupt files but was unable to fix some of them.
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
 
==================================================================

    Started on Sun 09/19/2021 at  1:12:55.20 

        [DISM /online /cleanup-image /ScanHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.1165 
 
The component store is repairable.

The operation completed successfully. 
 
==================================================================

    Started on Sun 09/19/2021 at  1:18:47.50 

        [DISM /online /cleanup-image /RestoreHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.1165 
 
Error: 0x800f081f

The source files could not be found.  
 
Use the "Source" option to specify the location of the files that are required to restore the feature. 
For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. 
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
 
==================================================================

    Started on Sun 09/19/2021 at  1:35:35.00 

        [SFC /ScanNow] 

Beginning system scan.  This process will take some time.

Results: 
 
Windows Resource Protection found corrupt files but was unable to fix some of them.

For online repairs, details are included in the CBS log file located at 
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
 
==================================================================

A TXT file named SFC_details.txt has been created on the desktop.
 
==================================================================

    Started on Sun 09/19/2021 at  2:02:29.35 

        [ChkDsk /Scan]  
 
The type of the file system is NTFS.
Volume label is Windows.
 
Stage 1: Examining basic file system structure ... 
765184 file records processed.                                                        
File verification completed.
Phase duration (File record verification): 13.01 seconds.
10435 large file records processed.                                   
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.04 milliseconds.
 
Stage 2: Examining file name linkage ... 
790 reparse records processed.                                      
1038600 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 53.37 seconds.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 2.60 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 0.12 milliseconds.
790 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 5.11 milliseconds.
 
Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
Phase duration (Security descriptor verification): 88.43 milliseconds.
136709 data files processed.                                           
Phase duration (Data attribute verification): 0.06 milliseconds.
CHKDSK is verifying Usn Journal...
39954784 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 377.82 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
722633727 KB total disk space. 
192370756 KB in 382078 files.
347680 KB in 136710 indexes.
0 KB in bad sectors.
898883 KB in use by the system.
65536 KB occupied by the log file.
529016408 KB available on disk.
 
4096 bytes in each allocation unit. 
180658431 total allocation units on disk.
132254102 allocation units available on disk.
Total duration: 1.15 minutes (69477 ms).
 
==================================================================
 
    Started on Sun 09/19/2021 at  2:04:01.86 
 
AutoReboot   
 
FALSE       
 
==================================================================
 
        [Set AutoReboot = False] 
 
Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'

Property(s) update successful.

==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'

Property(s) update successful.

==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=30720
CurrentUsage=18
Description=C:\pagefile.sys
InstallDate=20210123182308.249920-360
Name=C:\pagefile.sys
PeakUsage=18
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-K2CP43S"'

Property(s) update successful.

==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on Sun 09/19/2021 at  2:04:02.77

Code:

2021-09-19 01:10:43, Info                  CSI    00000174 [SR] Cannot repair member file [l:34]'System.Web.ApplicationServices.dll' of System.Web.ApplicationServices, version 4.0.15805.295, arch amd64, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-09-19 01:10:45, Info                  CSI    00000176 [SR] Cannot repair member file [l:34]'System.Web.ApplicationServices.dll' of System.Web.ApplicationServices, version 4.0.15805.295, arch amd64, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-09-19 01:10:45, Info                  CSI    00000177 [SR] This component was referenced by [l:78]'Package_3_for_KB5004331~31bf3856ad364e35~amd64~~10.0.4400.1.5004331-92_neutral'
2021-09-19 01:10:45, Info                  CSI    0000017a [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\\System.Web.ApplicationServices.dll; source file in store is also corrupted
2021-09-19 01:10:45, Info                  CSI    0000017b [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\\System.Web.ApplicationServices.dll; source file in store is also corrupted
2021-09-19 01:10:45, Info                  CSI    0000017c [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\\System.Web.ApplicationServices.dll; source file in store is also corrupted

zbook said:

Code:

A TXT file named SFC_details.txt has been created on the desktop.

If the TXT file were blank, the following sentence should have been written into "Tuneup.log".

Code:

SFC_details.txt is blank and has not been put onto the desktop.

zbook said:

Please modify so that it works similar to V2 and always creates a new location of the file on the desktop.

What do you mean by "a new location"? Do you mean a file name with a timestamp?

zbook said:

New titles on the desktop generally appear in the first opening on the left side.

I don't know what you mean. Please post a screenshot.

On my desktop there are a lot of files, folder, and icons.

When a file is replaced no new icon appears.

Then I must use everything search to locate the file.

Using V2 I never have to use everything search as it creates a new file in a new row or new column.

It's always the newest entry on the desktop on the left.

So when running a script the results can appear in the location of the prior file or in a new location on the desktop.

If it appears in the old location then it will be in the desktop clutter.

If it appears in a new location then it will be easy to find.

Can the scripts be modified so that they always create a new file in a new desktop location?



If you need an image of a row or column of desktop files, folders, or icons they can be posted.

I can put both "Tuneup.log" and "SFC_details.txt" into a ZIP file with a timestamp when SFC_details.txt has been created. Such a ZIP file will be considered a new file as the timestamp is different.

If that creates a new file on the desktop instead of replacing an old one it will be easier to find.