This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
This issue cropped up immediately after Windows Update installed two definition updates for Windows Defender consecutively. Windows Update started offering definition 1.193.3002.0 after the definition updates were installed, which was unexpected as a later version was installed through the updates. After installing 1.193.3002.0, Windows Update offered update 1.193.3192.0, and started offering 1.193.3002.0 immediately after installing 1.193.3192.0. I do have a recent system image backup (stored in another partition). I have tried manually resetting Windows Update (using the instructions I found on Microsoft Support) to no avail. I have restarted my computer multiple times. Both sfc and DISM found no problems with my computer. I downloaded and installed MBAM (free version) and ran a scan with it, which did not turn anything up. Should I just restore my computer from my system image backup?
<edit>
the Windows Defender UI indicated that update 1.193.3192.0 is installed. However, Windows Update is still offering (and automatically installing and looping) update 1.193.3002.0
</edit>
<edit>
I am running Windows 8.1 64bit with all updates (except for the pesky definition updates thingy) installed. I had a McAfee trial thingy installed quite some time ago, but I uninstalled it and ran MCPR (from the McAfee site) afterwards. I haven't made any changes to my computer in the past couple of weeks.
</edit>
<edit>
Turning Windows Defender off, restarting, and turning it back on did not resolve the problem. Dangit.
</edit>
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Sounds like that's probably the same issue.
I guess the good thing is this is probably widespread. Probably the only reason more people aren't posting here yet is most probably have autoupdates turned on.
I feel better when it's not just me as hopefully it means it'll get fixed LOL
Okay, a THIRD Windows 8.1 64-bit system is doing the exact same thing for me.
POSSIBLY my Surface 1 with 8.1 RT isn't doing it, but it's looking like 100% of regular Windows 8 systems are doing this. (At least ones running Defender.)
If you decide to "wave the white flag" this might give you some "peace" of mind.
If you switch off Automatic Updates and set them up to not download and only notify you then it is possible to hide a troublesome update. After doing such a thing you may return to your normal Automatic Update settings.
Control Panel\All Control Panel Items\Windows Update\Change settings
Hide Windows 7, or 8, Updates that you do not Ever Want to Install
My one and only Windows 8.1 VM is experiencing the exact same issue. It has literally nothing installed on it (it is a IE test VM thingy that I got from modern.ie). I tried rolling it back using virtualbox snapshots, but that did not resolve the issue. Is there anyone who is not experiencing this issue?
P.S. The Windows Update troubleshooter always finds problems and does stuff. (I verified this by running it on my friend's new ASUS computer and my IE test VM)
P.P.S. Since update 1.193.3002.0 is being reoffered on almost every Windows 8.1 installation, it is possible that Microsoft messed something up.
P.P.P.S. My friend's ASUS laptop just started experiencing this issue.
After renaming SoftwareDistribution and catroot2, Windows downloads definition update 1.193.3002.0 along with the latest definition update when it checks for updates. This indicates that Microsoft is still offering definition update 1.193.3002.0 for download. From this, we can conclude that Microsoft messed something up.
