Need Someone to take a look at my .CBS Files.

I was looking through my System Information Report under Windows Error Reporting and saw a lot of Windows Update errors. I was able to track them down to MSE definition update failures, this started back on January 21 of this year, and again on 3/5/2015. But it has recently gotten worse.

• Between 3/24 and 3/25 I had twelve failures.

• 3/26 to 3/27 eleven.

• 3/28 I had one that failed, one that took.

• Ever since then I've had six that installed okay.

Late on Monday the 28th I ran the updates troubleshooter, and MSFixit 50123.msi. I'd like to know if there is anything more seriously wrong so, could someone take a look at my .CBS and SysInfo logs please?

I have followed the posting instructions and completed steps #1 and #2; I never did receive any errors as shown for Step #3, the only way I found out about this is looking in the System Information Report under Windows Error Reporting.

The sysinfo log is before I ran the two troubleshooters on the 28th. The [Windows Error Reporting] is near the bottom.


Attachment 354619

There's no significant errors in the posted logs.
Errors installing MSE updates aren't uncommon - and are often caused because the system has actually already updated the target files.

Post your c:\windows\windowsupdate.log file and I'll take a look at that.

Thanks Noel,

That's good to hear! Yes I knew about the Hyphenation-English and Windows-IE-Spelling problems, do you think the IE spelling problems would lead IE10 to crash/try to recover? It seems to be doing that lately. I think I'm going to try running without a spell-checker add-on, on it for a while and see if that helps IE.

That's the strange part about MSE its been rock solid up until that January fail then it snowballed.

Here's the file you wanted: WindowsUpdate.zip I'm going to be out for awhile, won't be back till about 7-8pm your time so, no hurry.

Looking at that log, it's a little concerning
All the errors are of the -643 type - which has an unknown cause, but is probably related to a combination of file and registry problems.

My standard advice for any serious problems with MSE is to uninstall and attempt to reinstall, and I think that this treatment is probably a good idea here - you may also need to run the manual/forced removal tool before it goes back in.

How to manually uninstall Microsoft Security Essentials 2.0.1963 if you cannot uninstall it by using the Add or Remove Programs item

I'll start working on doing the uninstall then reinstall of MSE. I already d/l'd a fresh copy of MSE, backed-up the registry and printed the instructions from your link.

Just verifying; I noticed the instructions are for MSE v2.0.1963 and I'm up to Client v4.7.205.0; Instructions still valid for my version?


When done would you like a fresh set of .CBS both SUR and windowsupdate logs immediately after the reinstall or should I wait a day or two to allow MSE a chance to update itself then upload the logs?


I'll try and have this done today, but might not be able to post results until tomorrow. I'm setting up for new flooring in the kitchen, dinning room and TV rooms and it takes time to get organized, I wish this was a new 'empty' house.

Ah - let me hunt around...
This tool removes v2.x and higher, according to BleepingComputers...
http://download.microsoft.com/downlo...Fixit50692.msi

Before we go any further; I realize I should have waited until you answered my question about your MSE v2 tool link, but I do not have control over asstime while I'm trying to co-ordinate my flooring job. I just wanted to let you know that there could be delays.....

Being as such, since the last time we touched, I took the initiative to uninstall MSE thru 'Programs and Features', once I started the procedure it worked for a few minutes and closed. I know I did not have to manually do a cleanup using your previous link if that worked, but I thought 'oh what the heck since I have it I ran the fixit also.

The uninstall and fixit went well and at the end of the fixit cleanup there were three generic questions that I thought I didn't need to bother MS about (they pertained to my 'windows experience') so I closed that out, and......I,

I reinstalled MSE and allowed it to start windows firewall/defender and then do a quick scan, MSE was red until the definitions were D/L'd, but, during that DL it turned green before it started the scan and, the scan was clean.

New 'about page for the new MSE' :



I do apologize if I interrupted your thought process while helping me Noel and if I deserve a licking, I'm prepared for it and. Another un-re-install of MSE using your new find.

If not, what logs and timeline for those logs would you need?


Steve

No problem - you did exactly what was needed, so with any luck you won't have too many problems with MSE in the future

Keep an eye on it for a few days and see how it behaves.

Okay Noel, thanks for taking the time to search for the newer version of your tool link, I saved the link, in case.
There was one definition update (DU) yesterday and one today, both show successful in history. I'll get back to you sometime Tuesday for a behavioral update.

Noel, looks like MSE is okay now, I've had six definition updates since a week ago and they were all successful.