Windows 10: doing a dism restorehealth every month

I am using Windows 10 home edition.1909 OS build 18363.900 each month or after 3 months or so I am forced to do
Code:

my laptop occasionally becomes very slow for some unknown reason.
Like I face challenges when Microsoft Office starts loading it takes lot of times to open files.
Working with VMware virtual machines worth 500 Gb could be slow which is understandable.
But system boots very slow that is not understandable.
Usually when I run these commands vmware breaks and I have to re install vmware.Apart from that there has not been any other problem.
When I run these two dism commands things come back to normal and system is able to restore its health.
I want to know why is this happening. What is causing my laptop to be slow and why I need to regularly keep executing those 2 dism commands.

:)

 

How to get damn DISM to work?

Yes, I have the image mounted, the same bloody image I've used to install the OS I'm just using. This is absurd. I've tried this:

Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1 /limitaccess

None of this crap works even though entire freaking internet is saying that this is the way to do it. Some even mention using quotas for the path which makes no difference (It doesn't need it anyway since there aren't any spaces anyway.

I just can't understand how can OS integrity check tool feature be dumber as years pass by instead of being smarter and more useful.

EDIT:
Redownloading 4 gigs of stupid image because the one I have apparently isn't good enough. *sigh*

 

Error DISM restorehealth

Hello i just registered after i read all the pages...so opencl.dll is a problem of a windows update? Because i had no issues running sfc/scannow last month
**UPDATE**
Thanks it worked perfectly fine and it fixed any corrupted files.This worked perfectly...it was giving me a headache.Step 3 option 2 converted .esd file to .wim...! Thanks again guys.
step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source (OPTIONAL because step 3 already fixed the issue)

 

Error DISM restorehealth


twp things..

Executing command line: Dism /Online /Cleanup-Image /RestoreHealth /Source:"D:\Users\Hali\Downloads\IMAGE_HEALTH\IMAGE_HEALTH_SXS\Temp\Mount\windows\winsxs" /LimitAccess

Place the "Image_health" folder on C - you are running the command 9 folders deep...
Place Image_health-sxs.cmd inside "image_health" folder
Image health sxs cmd was and is only a TEST cmd
Image-health is the normal cmd...

[removed]

"C:\Windows\Logs\CBS\CBS.log" post the CBS.log

Also dism /scanhealth gives a better file report in the dism.log

Your damaged files appear to be that from a windows update, as windows update files are not on setup media..

step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source
step 5 post dism.log and cbs.log (note: you can post logs as .txt > cbs.txt dism.txt)