Windows 7: Security monthly quality rollup kb4525235 failing to install

rbhall52 · 2 Weeks Ago

I have been trying to get the KB4525235 update to install, but without success. I have windows 7 home premium 64-bit with 6gb of ram. I even downloaded and tried to install the update manually, but without success. What can I do to get this quality rollup update to install?

iko22 · 2 Weeks Ago

Hi rbhall52,

KB4525235 requires updates KB4490628 and KB4474419 to already be installed on the system beforehand.

rbhall52 · 2 Weeks Ago

I just checked, and they were successfully installed in september and last week.

Snick · 2 Weeks Ago

Hi rbhall52,
Let's see what the logs say.
Probably a corrupt install of prior KB.
Please download, place on desktop and run AutoSURT64.exe from my OneDrive
Folder will be too big to upload, remove the .cab files (they are compressed CBS.logs don't need)
Zip/Compress the folder and upload please.
Bill

rbhall52 · 2 Weeks Ago

Unfortunately, I get the following errors in the window that runs AutoSRT64:

Extracting files to C:\windows\Temp folder
Extracting from AutoSURT64.exe
Cannot create folder CheckSUR
Cannot create folder CheckSUR\servicing
Cannot create folder CheckSUR\servicing\Packages
Cannot create folder CheckSUR\WinSxs
Cannot create folder CheckSUR\WinSxs\Manifests

Snick · 2 Weeks Ago

OOPS, didn't check!

You need the 32 bit version, AutoSurt32
Sleep disorder, fun!

rbhall52 · 2 Weeks Ago

Here is the compressed folder without the cab files.

Snick · 2 Weeks Ago

No CBS.log
CheckSUR.log errors are Avast
update reminants

Code:

Checking Component Store
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_9c229ed3ddb17764    x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_9c229ed3ddb17764    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_5ca6eb17137337f1    amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_5ca6eb17137337f1    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_97429ce1e0dd4831    x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_97429ce1e0dd4831    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_a93423e024c3902a    x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_a93423e024c3902a    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_547567fcc9354e5e    amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_547567fcc9354e5e    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_4f95660acc611f2b    amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_4f95660acc611f2b    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_6186ed0910476724    amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_6186ed0910476724    
(f)    CSI C Mark Deployment Not Marked    0x00000000    c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_a45421ee27ef60f7    x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7

Click

copy and paste
C:\Windows\Logs\CBS
into Searchbox
May have removed cbs.log (can be up to 50MB) along with .cab files
Bill

Snick · 2 Weeks Ago

Here's the Avast fix avastclear.exe.
Download and place on desktop, run. It will prompt you for safe mode, yes. In safe mode choose your version, mine is Avast Free. Reboot. run Ninite Avast below and it will reinstall the newest version. If you have paid version, make sure you have your key.

Ninite Avast One click default installer
If you have an issue with being offered dual boot Win7 & Avast Clear, EasyBCD will permit removing 2nd boot option. It happens when avastclear offers you restart, you choose yes, and it doesn't. If that happens restart manually and it will enter safe mode.
Bill

FYI: Avast has been repeatedly notified of the their program updater errors, (CSI C Mark Deployment Not Marked) with no resolve so far. Seemed to start around the time of merger Avast/AVG. Yes, sometimes it does cause Win Update issues, sometimes, not always.

rbhall52 · 1 Week Ago

I tried to upload the compressed cbs log, but it is still 24.8mb in size, so perhaps I can upload it to my dropbox account and send you a link. I will do the other things you mention this morning in a bit.