I also have this problem on 2 desktop running Winows 8.1 X64 pc's. Definition 1.193.3002.0 keeps installing over and over and over since March 18. I think it had something to do with the fact that Update KB2962409 (which had previosly been installed back in June 2014) was offered, then removed by Microsoft on March 18. Someone evidently recognized a problem and withdrew that Update on March 18 or 19, but left the remnants of the screw-up. That is just a guess on my part, but anyway I also still have multiple Windows Defender Updates now because 1.193.3002.0 is being installed repeatedly. Fortunately, the pc's seem to be running ok and SFC /Scannow does not show any corruption, nor does DISM. And, no virus or malware is indicated by Malwarebytes or Hitman Pro or MRT.
Windows Update issue - Definition Update reoffered
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>
Windows for home | Previous Windows versions | Windows update
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.
74 answers
Sort by: Oldest
-
Anonymous
2015-03-21T12:06:00+00:00 -
Anonymous
2015-03-21T12:31:04+00:00 That is not the case for me. My system image was created on the 12th of march (with all updates installed)(I verified that it was fine by running dism /online /cleanup-image /scanhealth, sfc /verifyonly, and a full scan on the C drive with MBAM after I created the image). I restored the system image around an hour ago, which means that my system cannot have any update offered and pulled on March 18 installed. In addition, my system (before the system image restore) was able to install definition updates perfectly fine until the issue with definition 1.193.3002.0 cropped up. Do note that my current installation (the one restored from the system image made on the 12th of march) has this issue too, which means that any update offered and pulled on the 18th of march could not have caused the issue for me.
-
Anonymous
2015-03-21T12:54:57+00:00 That is not the case for me. My system image was created on the 12th of march (with all updates installed)(I verified that it was fine by running dism /online /cleanup-image /scanhealth, sfc /verifyonly, and a full scan on the C drive with MBAM after I created the image). I restored the system image around an hour ago, which means that my system cannot have any update offered and pulled on March 18 installed. In addition, my system (before the system image restore) was able to install definition updates perfectly fine until the issue with definition 1.193.3002.0 cropped up. Do note that my current installation (the one restored from the system image made on the 12th of march) has this issue too, which means that any update offered and pulled on the 18th of march could not have caused the issue for me.
As I stated, that was just a guess on my part - probably only coincidental - I shouldn't have mentioned that part (KB2962409) it just confused the issue. However, I still have repeated installs of Windows Defender Definition 1.193.3002.0. Probably not important since neither you or I seem to be having other problems. (Virus, malware, scanhealth, etc are all ok) Hopefully MS will sort it out eventually. Maybe this Summer when Windows 10 is offered, if not sooner.
-
Anonymous
2015-03-21T13:10:03+00:00 Thank you for clarifying your previous post :). I searched around the net and found a relevant entry on a Japanese site http://freesoft.tvbok.com/cat97/2015-2016/kb226760.html (I translated it using Google Translate). It pertains to issues with definition update 1.193.3002.0. (it does not offer any solutions) It appears that we are not alone, and that this issue is relatively widespread. I checked on a few friends' Windows 7 comps running MSE, but they did not exhibit any issue related to definition updates for MSE.
<edit>
I found another article on another (japanese) site that pertains to definition update 1.193.3002.0:
http://jisakutech.com/archives/25084802.html
its title is "
"
(translated by crappy Google Translate)
which does seem pretty relevant. There were many references to definition update 1.193.3002.0 in the article, so well.
</edit>
P.S. Bing did not turn up anything relevant when I searched "1.193.3002.0", "Windows Defender update loop", "Windows Update loop", and permutations thereof, so I used Google, which found quite a few relevant results, some of which I linked in this post.
P.P.S. Bing translate did a better job translating the article.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more