P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 20, 2023 #61 For some reason the dism command cannot download from Windows Update. Download Farbar Service Scanner and save the file on your Desktop. Right-click FSS and select "Run as administrator". Put checkmarks at following items only: Internet Services Windows Firewall System Restore Security Center/Action Center Windows Update Windows Defender Click Scan. A log file called "FSS.TXT" will appear on your desktop when the scan is finished. Attach this file to your next reply.
For some reason the dism command cannot download from Windows Update. Download Farbar Service Scanner and save the file on your Desktop. Right-click FSS and select "Run as administrator". Put checkmarks at following items only: Internet Services Windows Firewall System Restore Security Center/Action Center Windows Update Windows Defender Click Scan. A log file called "FSS.TXT" will appear on your desktop when the scan is finished. Attach this file to your next reply.
mathphilip Active member Joined Mar 30, 2023 Posts 38 Apr 20, 2023 #62 Here it is. Observation: I use Kaspersky Antivirus. May be the reason Windows Defender is disabled. Attachments FSS.txt 2.6 KB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 21, 2023 #63 Step 1: 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 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. Step 2: Restart the machine. Run the command sfc /scannow in an elevated commandprompt and report the result. If it fails attach the file cbs.log to your next reply. Attachments SFCFix.zip 169 KB · Views: 4
Step 1: 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 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. Step 2: Restart the machine. Run the command sfc /scannow in an elevated commandprompt and report the result. If it fails attach the file cbs.log to your next reply.
mathphilip Active member Joined Mar 30, 2023 Posts 38 Apr 21, 2023 #64 Windows Resource Protection found corrupt files but was unable to fix some of them. Attachments CBS.zip 90.2 KB · Views: 1 SFCFix.txt 25.8 KB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 21, 2023 #65 Step 1: 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 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. Step 2: Restart the machine. Run the command sfc /scannow in an elevated commandprompt and report the result. If it fails attach the file cbs.log to your next reply. Attachments SFCFix.zip 2.7 KB · Views: 4
Step 1: 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 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. Step 2: Restart the machine. Run the command sfc /scannow in an elevated commandprompt and report the result. If it fails attach the file cbs.log to your next reply.
mathphilip Active member Joined Mar 30, 2023 Posts 38 Apr 21, 2023 #66 No integrity violations. \o/ Attachments SFCFix.txt 7.8 KB · Views: 0 CBS.zip 150.7 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 21, 2023 #67 Great. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
Great. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 22, 2023 #69 Great. Any remaining issues ?
mathphilip Active member Joined Mar 30, 2023 Posts 38 Apr 22, 2023 #70 It's all good, Peter! Once again, thank you very much for your help. All the best to you!
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,668 Apr 22, 2023 #71 Your welcome. Take care.
mathphilip Active member Joined Mar 30, 2023 Posts 38 Apr 27, 2023 #72 [Update] I was able to fix the initial issue (slow Windows startup) by disabling the "fast startup" feature in the power settings (which is ironic ). Apparently there was a problem with the hibernation file (hiberfil.sys). Just a possible solution for those who are experiencing the same problem and find this thread.
[Update] I was able to fix the initial issue (slow Windows startup) by disabling the "fast startup" feature in the power settings (which is ironic ). Apparently there was a problem with the hibernation file (hiberfil.sys). Just a possible solution for those who are experiencing the same problem and find this thread.