Solved Previously installed Win Defender update keeps appearing

A definition for Windows Defender was installed as shown:
Definition Update for Windows Defender - KB2267602 (Definition 1.193.3002.0)
Installation date: ‎3/‎20/‎2015 8:55 PM
Installation status: Succeeded
Update type: Important

Currently Windows Defender is updated (today) to:
Definition Update for Windows Defender - KB2267602 (Definition 1.193.3369.0)
Installation date: ‎3/‎21/‎2015 8:19 AM
Installation status: Succeeded
Update type: Important

Between those two definitions--KB2267602 (Definition 1.193.3314.0) and KB2267602 (Definition 1.193.3363.0--were installed.

The installed updates list shows the .3002 shown above installed more than once, for example. Even after the "newest" (.3369) update shown above, it still appears as an update (Win Defender) to be downloaded. Odd, right?

Should I do a system restore to a point before the .3002 update? Is there another solution? This has not happened before.

Other than that, the Windows Defender program itself shows the latest definition in the update tab (.3369).

Hello CPWin8,

If you like, you could hide the Windows Update to no longer see it available to install.

Windows Update - Hide or Restore Hidden Updates - Windows 7 Help Forums

Brink said:

Hello CPWin8,

If you like, you could hide the Windows Update to no longer see it available to install.

Windows Update - Hide or Restore Hidden Updates - Windows 7 Help Forums

Click to expand...

Thank you, Brink. I saw that option to "hide" when viewing the list of updates. I wasn't sure if there was some kind of problem with the update system. I guess I can try using a restore point prior to noticing the issue. For example, last year or the year before there was a bad Defender update (there is an old thread for it on here somewhere) put out where the fix was to manually download and install the definition update. I couldn't find anything regarding that, and thus I figured I should inquire about the issue in general. In that case Defender did not work properly. In my case, it seems to operate properly. It is just that "leftover" old/previously installed definition.

Thanks.

You're welcome.

Hiding the update would be the easiest option to stop it.

You could also see if resetting Windows Update may stop it without having to hide it.

Windows Update - Reset - Windows 7 Help Forums

Brink said:

You're welcome.

Hiding the update would be the easiest option to stop it.

You could also see if resetting Windows Update may stop it without having to hide it.

Windows Update - Reset - Windows 7 Help Forums

Click to expand...

The problems are piling up. My system seems to work fine (other than that odd Defender issue), but I just ran the system restore. It failed--on two separate instances. The first time it said it could not copy the registry (I didn't take screenshot). The second says, "System restore failed while scanning the file system on drive C:\ The drive might be corrupt." See screenshot attached.

I ran sfc /scannow and chkdsk c: and had no problems. See attachedpic if details of scans are needed.

The only changes I've made to the system (aside from saving normal files or web browsing) were the monthly Windows updates. I didn't see any problem there. I wonder if the two problems are somehow connected but one could never figure the connection out. I haven't used system restore in a long time and previously, it worked fine.

I will use your suggestions for now to deal with the Defender issue at the moment because this system restore issue is beyond me.

Thanks.

Did you try doing a system restore again after running chkdsk?

Yeah, I'd say hiding the update would be the best way.

Sorry. My thread has jumped itself from security to maintenance. Yes, I tried it after the chkdsk c:. It still comes up with the same system restore point errors.

I have "hidden" the (.3002) definition that keeps appearing for Windows Defender definitions. Defender has now been updated to .3404 (most recent found by Win updates). Should I mark the thread as "solved" based on that result from that approach to "eliminating" it?

The dialog box from the System Restore error says can retry after trying chkdsk /R, but when I tried that, it says it can't lock the drive and asks if I want it to run it (y/n?) next time Windows restarts. That is why I only used chkdsk C: and that said, as noted above, no problems were found. Thank you again.

I'd say you're good to go for the Windows Defender definition issue.

As for System Restore, I'd personally use system images to be safer. They are more reliable than just using restore point.