New
#21
These are examples of scannow problems that were detected and would not have been detected by running restorehealth before scannow:
BSOD after Wakeup from Standby (DRIVER_POWERSTATE_FAILURE)
(post #6)
Upgrade to 2004 green sceen driver_pnp_watchdog - rolls back
(post #49)
Can't Load Into Windows 10 Normally
(post #14)
I have a fairly large number of asd64 Microsoft files going back to 2019. I understand it is not safe to delete them all nor to delete the folder. Can DISM be of use in reducing the size of this folder ? I am not short of space but suspect old files are causing some of the trouble I have been having and am looking for old files I can safely delete.
I have problems using DISM. I have tried syntax forms -DISM /Online and DISM.exe /Online. Sometimes Windows 10 rejects Online Image, sometimes it rejects Clean-upImage. I am careful to add a space prior to each / . I read on another ten forums link that winsxs might be corrupted but oddly when i entered the suggested DISM command, using copy and paste, to check this it worked and I got the result no problems with winsxs.
Can you suggest any reason for this. DISM has worked in the recent past on this laptop with this Windows build. sfc /scannow worked and returned result no problems but I am unconvinced and would be much happier if I could use DISM to check.
I would like to try Navy Guy`s suggestion of command findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > "%userprofile%\Desktop\sfcdetails.txt" (cannot get rid of italics using FONT)
but I am very new to this - I assume I need to substitute something for SR ? And do I need the inverted commas and brackets around SR and inverted commas round last section? Just in case, I tried it as it stands and it was rejected.
Please run this script:
Batch files for use in BSOD debugging
If you find any problems in the results you can open a new thread.
Thank you for your reply.
I am sorry but lack of experience of forum and BSOD prevents me from following your instructions.
I assumed I needed to open a new thread in BSOD Crash Forum to paste 2 lines from the BSOD tutorial to point users to the BSOD threads. I tried to open a new thread twice but after leaving it to copy the lines to be pasted in, I could not find any reference to my new thread either in General or BSOD Forums. But I have just noticed in summaries below that the path to be entered first has been expanded to
Batch files for use in BSOD debugging
Submission of this reply results in above being replaced by
a Batch direction.
Parts of my text are disappearing.
What is the correct order of DISM and sfc commands to fix problems?
Click on the batch file link in the above post.
Then scroll down to:
Code:Part One Download the batch file Download the batch file to your Desktop or Downloads folder. Download �� Tuneup_plus_log.bat ✔️ 【Last updated on September 24, 2021】
Run the download and click permissions as needed so that it can run.
https://www.tenforums.com/attachment...p_plus_log.bat
There will be a pop up when it completes indicating that there is a text file on the desktop.
If there are problems you can open a separate thread.
Sorry again. This is all I have in Part 1.
Part One
Download the batch file
To install the Context Menu options and backing batch support, download this batch file.
DownloadAddGenFileList.bat
No response to clicking on Download.
I started this at 4 am so I need a break ! Am falling asleep.
Many thanks. Back later.
PP
Be guided by the SFC tutorial.
SFC - TenForumsTutorials
- Guidance for extracting SFC results is given in its Option 5***. This is only useful if SFC reports that there were faults. If SFC has not reported any faults then there will be nothing in the results worth looking at.
- The normal procedure for running SFC is given in Option 3 and the suggestion for then running Dism is explained in a note at the end of that option. If you do use that Dism command then use it exactly as given and make sure you are online when you run it because it accesses MS servers to find good copies of system files.
*** You need not change anything in the command in Option 5 except for any change that you might want for the results file path
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
or, say,
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"C:\Fred\Desktop\sfcdetails.txt"
or, say,
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"D:\Desktop\sfcdetails.txt"
- In all cases, check that the folder path you are using exists.
- If the results file path-name does not include any spaces or special characters [such as an ampersand] then you do not need the " around it but including them never does any harm so you might as well leave them in.
- Do not change the "[SR]" part at all.
If you use the PowerShell form of the command then don't change anything.
All the best,
Denis
Dism is a very sophisticated command. Much of its use is explained in
Use DISM to Repair Windows 10 Image - TenForumsTutorials
Best of luck,
Denis