Platinum Lucario
Active member
- Apr 1, 2017
- 39
Not too long ago, I had some SFC and Windows Update corruptions due to bad RAM, which have now been fixed in an earlier thread that I made.
So now that my Windows Update and SFC issues are out of the way. I did a test run to install updates today on the same machine, only to notice that the updates successfully installed, and even says that it successfully installed in the history log. But the updates don't show up in the installed updates area, and the updates will just keep re-appearing.
These updates, are mainly Office-related updates, which I don't even have any Microsoft Office programs installed on the OS. So from what I can see, it thinks there is Office entries, but when it installs, it can't find the folders.
Normally this should result in an error, but it doesn't, and instead just results in a "Update Installed Successfully" and even shows "Successful" in the Update History, but it's not in the installed updates though.
So I ran a Process Monitor, then I viewed the results. Many of the processes come back saying "NAME NOT FOUND" in the result category. I remember long ago when I tried to uninstall Microsoft Office 2003 manually (without requiring the disc), which would've been part of the problem. The only leftovers of Microsoft Office 2003 I didn't remove, were the registry entries, which would also be contributing to the issue that I'm having with the updates.
If anyone wants to take a look into the first PML file, you're more than welcome to. It's right here!
The next issue I have regarding problems installing updates, is actually to do with Microsoft Security Essentials itself. For one thing, if attempted to install, it will fail with error code 8004FF80. The one thing I noticed in the Process Manager with this one, is that there shows some results saying "BUFFER OVERFLOW" with the process UpdateInstall.exe. Also, attempting to uninstall MSE will also result in the same error code. So I'd say there is possibly some corrupt entries with MSE as well. I'd say that it also got damaged by bad RAM in the past as well. If anyone wants to take a look at the PML for this error, here it is!
I also ran a dism /online /cleanup-image /scanhealth. And everything seems fine except for Avast-related files. Here's the output of Checksur.txt:
So looks like, there's still more corruptions that need to be fixed, which probably lurk outside of Windows Update and SFC. Mostly to do with programs that don't exist and MSE.
So now that my Windows Update and SFC issues are out of the way. I did a test run to install updates today on the same machine, only to notice that the updates successfully installed, and even says that it successfully installed in the history log. But the updates don't show up in the installed updates area, and the updates will just keep re-appearing.
These updates, are mainly Office-related updates, which I don't even have any Microsoft Office programs installed on the OS. So from what I can see, it thinks there is Office entries, but when it installs, it can't find the folders.
Normally this should result in an error, but it doesn't, and instead just results in a "Update Installed Successfully" and even shows "Successful" in the Update History, but it's not in the installed updates though.
So I ran a Process Monitor, then I viewed the results. Many of the processes come back saying "NAME NOT FOUND" in the result category. I remember long ago when I tried to uninstall Microsoft Office 2003 manually (without requiring the disc), which would've been part of the problem. The only leftovers of Microsoft Office 2003 I didn't remove, were the registry entries, which would also be contributing to the issue that I'm having with the updates.
If anyone wants to take a look into the first PML file, you're more than welcome to. It's right here!
The next issue I have regarding problems installing updates, is actually to do with Microsoft Security Essentials itself. For one thing, if attempted to install, it will fail with error code 8004FF80. The one thing I noticed in the Process Manager with this one, is that there shows some results saying "BUFFER OVERFLOW" with the process UpdateInstall.exe. Also, attempting to uninstall MSE will also result in the same error code. So I'd say there is possibly some corrupt entries with MSE as well. I'd say that it also got damaged by bad RAM in the past as well. If anyone wants to take a look at the PML for this error, here it is!
I also ran a dism /online /cleanup-image /scanhealth. And everything seems fine except for Avast-related files. Here's the output of Checksur.txt:
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-04-07 00:01
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144 amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_49391d6d8244622b x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_ef17e13d91c55d96 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_36c51814a641869c x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_020285fe6d6e0580 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2
(f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_364e78aca69bba41 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_49afbcd581ea2e86 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8
Summary:
Seconds executed: 676
Found 8 errors
CSI C Mark Deployment Missing Total count: 8
So looks like, there's still more corruptions that need to be fixed, which probably lurk outside of Windows Update and SFC. Mostly to do with programs that don't exist and MSE.