Every one of the "gang of six" Windows Updates fails one way or another when run individually. BTW: both "sfc /VERIFYONLY" and "CHKDSK /F" report there is nothing wrong with my Windows partition and nothing wrong with my system files.
It fails during the Reboot Startup Configuring Update phase., so there is no error code posted. The %WinDir%\Logs\CBS\CBS.log is attached in the CBS Log.ZIP file.
Attachment 406974
Note this is how this single update has failed for some time now, after many attempts by MS Support technicians to get it to go.
This is an example the oldest optional update run from the 6 that continually fail, as a lone update request.
Here are the screen shots for the run.
Here are two ZIP files comprising the runs %WinDir%\Logs\CBS\CBS.log file, split into 2 parts to fit under the ZIP file upload limit.
Attachment 406980
Attachment 406981
I just took a quick re-read. Were you ever able to install the December and January updates. There was a problem in that Malwarebytes issued an update which caused a problem with installing the December updates. Removing Malwarebytes or reverting to an earlier version, caused the problem to go away. In January, Microsoft screwed the updates up. There was a fix for that but I'd have to try to find it.
Thanks for hanging in there with me, Wither 2. Pardon my ignorance, but what is "Malwarebytes" and where is it located (so I can delete it as suggested)?
It's once again disappointing that in my lengthy telephone interaction with Tier 2 Windows 7 Microsoft Support technicians, they never mentioned anything like this nor ever searched for "Malwarebytes" that I could observe while they were driving via their Remote Console control app. They never mentioned the CBS.log Win Upd tracing log or ever tried to capture an update session log, either.
It's also depressing that the Windows Update process is so unstructured, by E.W. Dijkstra's definition of truly structured programming.
All this has led me to conclude that MS Tech Support really doesn't know what is causing these Dec-2018-and-subsequent Windows Update problems and thus is clueless as to how to fix them short of blowing away all or parts of an existing Windows 7 installation.
To answer your direct question: No, I never was able to install the Dec 2018 or Jan 2019 Security-Quality rollups, nor were the MS Support people able to, either. Even the Windows Defender malware data updates wont install, not that I give a hoot about that. (I use far better malware protection, detection and correction software.)
Last edited by malletKATman; 17 Feb 2019 at 12:33. Reason: Adding material
Hi malletKATman,
Malwarebytes is a malware detector/scanner. It is available for free or real-time protection (premium paid version). If you didn't install it, it most likely is not on your computer. You can go to Control Panel > add remove programs and look for it.
Malwarebytes Cybersecurity for Windows, Mac, Android & iOS
Have you run sfc /scannow or System Update Readiness Tool (SURT)? If not, please do so! Be patient as they may take a while to complete. When SURT completes please upload CBS.log, most resent CBSpersist.cab & CheckSUR.log which will be temporary in its original location which is C:\Windows\Logs\CBS and WindowsUpdate.log location C:\Windows.
Last edited by Snick; 17 Feb 2019 at 17:16. Reason: add hyperlink
Hi Snick, thanks for responding to my thread.
As I have stated in this thread, I have run SFC repeatedly (usually with just the /VERIFYONLY option) and it always finds my system files intact. I also have run CHKDSK /F, which finds my system partition intact. I have tried to run SURT according to the posting rules for this forum, and it is truly weird. It asks it I want install <the update name>, I answer yes, it runs and finishes claiming success, but then I don't find the SURT program or anything else new to run: nothing new in the Programs list, no new desktop icons, etc. I click on "Windows6.1-KB947821-v34-x64.msu" that gets downloaded and I get the following screen:
If I answer No, it aborts. If I answer Yes, it runs for a long while with this screen showing
For some weird reason checksur.exe gets run off my F: USB-connected backup drive instead of from my C: Windows partition or my E: Winchester hard drive where "Windows6.1-KB947821-v34-x64.msu" is stored.
I'm running it now and will post all the logs when it finishes, as you requested.
Excellent!
System Update Readiness Tool (SURT) is a Microsoft tool that checks your system files, folders, manifests, & cat/mum files which was initially for upgrade installations of win 8, 8.1 and 10. It doesn't fix anything, it produces logs, CheckSUR.log and CheckSUR.persist.log which will be temporary at C:\Windows\Logs\CBS. It should appear in Windows Update as an Installed Update.
Running sfc /scannow more than once is unnecessary!
The "Installation/System Update Readiness" completes with an "Installation was successful" window: a bizarre way to run a program indented to check for update readiness. The logs you requested seem to show that the run was not a readiness check but rather an attempt to install some windows updates. The attached "SUR-RunLogs.zip" contain the log files you wanted.
SUR-RunLogs.zip
The only CBSpersist*.cab file I can find anywhere on my Windows partition is in a "C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.17601<blah,blah...>" folder, is named "CbsPersist_21090217152748.cab", is already compressed and enormous: 9.59MB. The most aggressive ZIP-like compression I can use reduces that by only 4% and produces a ZIPX - not a ZIP - file, which is not permitted as an upload. The only way I can get that cab file to you is by direct email or Dropbox. For either method I would need your private email address; for Dropbox the address would have to be attached to your dropbox.
As regards Malwarebytes: it is never been on my computer. I use Webroot SecureAnywhere as my malware protection software.
As regards multiple SFC runs: there have been times in this struggle when MS Support technicians have created some corrupt system files on my box while trying to force through updates. The last time it took three consecutive SFC /SCANNOW - Reboot runs to fix it all. So now I tend to run SFC /VERIFYONLY after every Windows Update run to check that something else didn't get corrupted. My trust in Windows Update runs of any form has gone the way of the people's trust in the federal government after Watergate.
Thanks for the logs, don't need persist now.
Summary:
Seconds executed: 649
Found 55362 errors
CSI Missing Deployment Key Total count: 2053
CBS MUM Missing Total count: 5
CBS Watchlist Package Missing Total count: 36588
CBS Watchlist Component Missing Total count: 16716
You have a misunderstanding of System Update Readiness Tool, which checks for issues before you upgrade windows. It detects missing, corrupt files/folders or registry issues that you currently have with your computer (55362 errors) It sometimes can repair some issues it finds i.e. below the (f) entry will be a (fix) entry meaning the error was corrected, usually missing files or folders. You have 5 missing mum files which SURT could not find a replacement, thus no (fix).
I could provide the 5 mums but it doesn't address 55000 other errors.
Let me do a little research on the correcting Watchlist Packet and Component errors.
Last edited by Snick; 18 Feb 2019 at 07:39. Reason: add last paragraph info after re-reading OP's post #1
Quote
