fits79,
I disagree with your assessment that Window Updates cause more problems that it solves. Of all my posts guessing 2,500 on Windows Update issues.
As I stated do not defrag an SSD, it is not needed and most of the time Windows will recognize and SSD and automatically disable auto defrag. Yes, you can manually defrag it but is is not needed and unnecessarily place wear and tear on of your drive. SSD have a limited read/write sequence, some more than others. Solid State Drives are similar to RAM except for the fact that they are not volatile memory as RAM, they are persistent, that is, they retain what is on them with or without power.
I understand that you are not interested in Windows Update, and that never was any focus of my dissertations with you . Do you understand what I said about SURT. It will identify the missing corrupt files in your OS. I am not talking about FIXING windows update. Most tools have more than one use. SURT is a diagnostic tool, and the main purpose is to make sure Win7 will upgrade to Win10. It also saves time perusing a CBS.log that can have 10,000 entries or more looking for an error or many. You don't have any idea how much time that takes.
Then if you have multiple corruptions, I have to manually search my repository for those file. I cannot use the CheckSUR.log because I don't have it. The CheckSUR.log list, at the very bottom of the log, all the unavailable repair files in winsxs folder. And you probably guess it, I have an automated tool that read the CheckSUR.log, locates the exact file, same version, exact same everything and copies it to a folder it creates on my desktop. The folder is named CheckSUR, the subfolder servicing and winsxs, the subfolders within them are in order that I listed the others servicing/Packages, winsxs/manifests. I place the CheckSUR.log on my desktop and click my Find Replacement Files.bat, CMD opens, folders appear on my desktop and notepad. The files I have go in the appropriate checksur subfolder, the ones I don't have, a text entry is placed in notepad and when finished, if there are any I don't have, I know exactly what I have to search for on the Net, or Microsoft Catalog. Sometime it takes a bit to find the correct KB they came from. Then you have to download that KB extract/expand the contents which can be 15,000 files or more and find the exact one. Yes, I have a batch script to do that too.
The purpose of me asking you to run SURT is to identify the specific files that sfc /scannow and or sfcfix cannot repair or replace because those file are missing from the winsxs folder.
Unless your system is free of system errors, I cannot guarantee that the issue you posted here in this thread can be rectified.
Quite often, attempting to rectify a problem without the sfc /scannow and sfcfix from reporting no errors is an exercise in FUTILITY. If I was being paid, no problem, I have clients all over the globe, most listen to those that know more on the subject matter then they do. The ones that don't, well, it gets expensive being that I charge. Depending on the issue, up to $100 per hour, 4 hour minimum.
6 pm here in Michigan, have to make dinner.
Snick