New
#951
It placed a new file on the desktop that was easy to find when there is clutter.
I've not yet tested the script on a computer without scannow problems.
These were the results with the latest version:
Code:Started on Sun 09/19/2021 at 16:23:38.63 [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 16:26:42.61 [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 16:30:02.91 [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 16:42:58.79 [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. ================================================================== Started on Sun 09/19/2021 at 16:45:51.06 [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.75 seconds. 10440 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.09 milliseconds. Stage 2: Examining file name linkage ... 798 reparse records processed. 1049854 index entries processed. Index verification completed. Phase duration (Index verification): 41.69 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 2.64 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 1.91 milliseconds. 798 reparse records processed. Phase duration (Reparse point and Object ID verification): 6.28 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 78.56 milliseconds. 142336 data files processed. Phase duration (Data attribute verification): 0.06 milliseconds. CHKDSK is verifying Usn Journal... 39143544 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 550.64 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 722633727 KB total disk space. 200332640 KB in 394171 files. 365236 KB in 142337 indexes. 0 KB in bad sectors. 898375 KB in use by the system. 65536 KB occupied by the log file. 521037476 KB available on disk. 4096 bytes in each allocation unit. 180658431 total allocation units on disk. 130259369 allocation units available on disk. Total duration: 58.74 seconds (58741 ms). ================================================================== Started on Sun 09/19/2021 at 16:47:09.65 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=351 Description=C:\pagefile.sys InstallDate=20210123182308.249920-360 Name=C:\pagefile.sys PeakUsage=382 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 16:47:10.65
Code:2021-09-19 16:45:47, Info CSI 00000467 [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 16:45:47, Info CSI 00000469 [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 16:45:47, Info CSI 0000046a [SR] This component was referenced by [l:78]'Package_3_for_KB5004331~31bf3856ad364e35~amd64~~10.0.4400.1.5004331-92_neutral' 2021-09-19 16:45:47, Info CSI 0000046d [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 16:45:47, Info CSI 0000046e [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 16:45:47, Info CSI 0000046f [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
The above output was incomplete. The bug has been fixed in the just updated version below:
👉 Tuneup_plus_log.bat ✔️ 【Last updated on September 20, 2021】
Windows keeps attempting an update.
When there is a pending update it will not run scannow.
So it jumped quickly to dism.
Code:Operation (2): DISM is scanning the image of Windows.
Try to control Windows Update via the following:
Using CMD script and VBScript to control Windows Update
Somehow BIOS updates were followed by Windows updates.
Currently an in place upgrade in clean boot is running (now at 59%).
Unfortunately, the script was not seen earlier as it could have been tested with another BIOS update.
I have posted it many times. I am surprised that you did not see it.
There were many boot failures.
I was happy that there were no more boot failures and had forgotten about sledgehammer.
After the in place upgrade I may update the BIOS again to see if it triggers an update during reboot.
If it does then I wonder if updates could still be blocked.
If the script is used how do you reverse it without a system restore?
↺ If you want to undo the changes made by the scripts, just double-click on "Undo_the_changes.vbs".
Source: Using CMD script and VBScript to control Windows Update
After the repair I'm running the scripts.
When available please post a new LOGS PS1 mini script for testing.