For the last 3 days Windows Defender Definition Updates (through Automatic Updates) have all failed with the error message:
“Definition Update for Windows Defender - KB2267602 (Definition 1.239.688.0) - Error 0x80070643”
Launching the Defender UI and updating definitions from there does work OK.
I haven’t made any changes to the system, but I have noticed that Windows itself is running scans and creating various 'Compatability" and other logs this week.
Presumably it is doing this to prepare for the Creators Update due next week.
With Windows 10 Defender is part of the OS and so you can’t uninstall/reinstall to try and repair errors.
What I’ve tried up to now-
I may try a restore point next, or may not.
If it is something MS have snafu’d in the lead up to the Creators Update then it’ll just do it again after the restore.
It’s no biggie, but I just wondered if anyone else is seeing this problem?
There's the .NET Framework Cleanup Tool - it's a sort of last resort so if you decide to use it first make a full system image before using it. I don't believe it will let you uninstall a version of .NET Framework that was pre-installed on the OS, so if you have an OS pre-installed version that's went corrupt the only fix may be to restore Windows after you've exhausted "possible fixes."
I only mention it because a few years ago that was the only way I could get .NET Framework to start updating properly again, i.e.; I had to uninstall every version .NET Framework Cleanup Tool allowed me to, and then install the versions of .NET Framework my system needed to run installed software. Using the .NET Framework Cleanup Tool didn't damage any of the software installations I had, however with Win10 your experience may be different if you use it.
You already tried the Microsoft .NET Framework Repair Tool (another link for it here). From my experience depending upon the damage and possibly the age of damage it may not help. I think the issue is there's so many security patches for .NET Framework that it just gets corrupted eventually. I'm surpised Microsoft hasn't made something like the .NET Framework Cleanup Tool themselves that allows a full uninstall of problematic versions so that end-users can reinstall it to have a working version.
TBH the Creators Update is only a week or so off so the OS is going to get a major update anyway.
I'm just going to ignore it until then and manually update the Defender definitions from within defender itself.
If the Creators Update doesn't fix it by itself then I'll probably download the ISO and do a complete reinstall from media.
Looking online this has been a recurring problem with Defender definition updates for years now.
I'm still guessing that this time it's to do with the Creators Update preparations.
I know that part of this update is going to be big changes to Defender and the Windows Security Centre, maybe they have installed/changed some component before they should have.
maybe they have installed/changed some component before they should have.
You'd think if it was pre-loaded on the machine waiting for the install date it would just be dormant and not cause any issues. If it is .NET Framework causing you issues a clean install of the OS would fix it, unfortunately the issues may return in the future. It's one reason I don't miss Windows Updates at all on this old unsupported XP machine.
Thanks everybody for all your input.
It probably wouldn't even be noticeable if Defender didn't put out definition updates a couple of times everyday. (Which of course is a GOOD thing and shows they are trying to keep on top of new malware).
Like I say I'm pretty sure this is all to do with the forthcoming creators update so I'm just going to ignore it for now.
Hazelnut,
That's interesting to see, at least it shows I'm not the only one seeing problems with Defender definition updates at the moment,
When I update definitions from within defender itself it works fine, it's just the automatic Windows updates that are failing.
I do note that the posters on that thread are in the USA.
Maybe MS are doing different things on different servers?
When I went to update it on my mother's Win10 laptop today 4/3/2017 something immediately killed the wireless connection, and there shouldn't have been any wireless connection issues because the laptop was about 12 inches away from the modem in clear sight. ![:huh:]()
I rebooted the modem, and the laptop, and then manually initiated a Windows Defender update and it updated to 4/1/2017 - well that beats the 3/23/2017 definitions she had on it which were 10 days old. She told me just install another antivirus on it, I told her to just wait and see what Microsoft does first before trying something else.
When I went to update it on my mother's Win10 laptop today 4/3/2017 something immediately killed the wireless connection, and there shouldn't have been any wireless connection issues because the laptop was about 12 inches away from the modem in clear sight. ![:huh:]()
I rebooted the modem, and the laptop, and then manually initiated a Windows Defender update and it updated to 4/1/2017 - well that beats the 3/23/2017 definitions she had on it which were 10 days old. She told me just install another antivirus on it, I told her to just wait and see what Microsoft does first before trying something else.
For some reason the Windows 10 Cumulative Update keeps killing wifi for some users, different users each time.
Last December they managed to knock millions of users in Europe off line.
http://www.bbc.co.uk/news/technology-38301548
Microsofts response to that one- issue a new update, which of course the affected users couldn't get because they had no connection. ![:wacko:]()
There again a few weeks ago I cleaned up a friends laptop and found it had not had any Windows Updates since she bought it, it still had version 1511.
I eventually worked out that is was AVG free that had been completely blocking Win 10 Automatic Updates.
Again it's a strange one, AVG will block Win 10 automatic updates on some supposedly 'identical' PCs but not on all.
Thank you for explaining the Wi-Fi issue. I thought my modem was dying again because it exhibited the exact same behaviour as it did about 1 year ago even on a wired connection when attempting to access something online boom the connection was dead and I was doing numerous daily modem reboots.
Where I live a modem usually only lasts 1-2 two years anyways do to all the thunderstorms and power outages that I think kills a modem which is why I will only rent them from my ISP who will promptly send a replacement in about 2 days instead of paying $100 or more for them to only have to re-buy them again in 1-2 years.
Hazelnut,
That's interesting to see, at least it shows I'm not the only one seeing problems with Defender definition updates at the moment,
When I update definitions from within defender itself it works fine, it's just the automatic Windows updates that are failing.
See top of this page
We are addressing limited reports about problems with automatic updates. To get the latest protection, manually install updates.
https://www.microsoft.com/security/portal/definitions/whatsnew.aspx
Thanks hazelnut,
I'm definitely now of the opinion that this is to do with the Creators Update and will probably sort itself after that.
I'm just deciding whether to wait till next week for the Automatic Update, or whether to go get it today via the Update Assistant.
This may help you through it nukecad
https://www.tenforums.com/windows-10-news/80993-creators-update-available-through-update-assistant.html
EDIT..
Looks like initially it wasn't too helpful (at the time of writing this post) ![:)]()
Cheers,
I’m still not decided yet whether to install it now or wait for the Automatic update.
As some have noted on that link you gave, if you are thinking of installing it early then you need the new version of the Update Assistant from Softpedia:
LINK REMOVED see post #15 below
(This version was briefly on the official MS site but was later removed again, its supposed to be going back on the official site later today).
I’ll probably leave it for now and think again tomorrow.
If I was that bothered about geting updates early I would have joined the insider ring.
Just to report that the original problem with Defender Definitions failing in Automatic Updates has now cured itself.
(Or rather MS released a fix a couple of hours ago).
I just noticed it going through as I was sat doing something else.
The new version of the Windows Update Assistant is now available of the offical MS website. (It's digitial signature is 04 April).
https://www.microsoft.com/en-us/software-download/windows10
If you already have WUA on your computer you may want to uninstall it before downloading the new one (I did).
Click on the "Update Now" to download the Assistant and then double click on the downloaded "Windows10Upgrade9252.exe"
It should tell you that you do not have the lastest build of Win 10, and that you can update to Build 15063 (which is the Creators Update) - and away you go.
I'm running it right now, but with my wifi maxing out at 7.2 Mbps it's going to take a while to download the update.
Running the upgrade too here nukcad as we speak.
Hope it works !! Am doing it with all my security tools running ![:lol:]()
Have an image it it all goes wrong.
Am doing it with all my security tools running ![:lol:]()
Don't forget your toast and golden coffee mug! ![:P]()
All working well with no issues so far ![:)]()
Followed this guide and it went exactly as it showed in the screenshots.
https://www.tenforums.com/tutorials/81031-update-latest-version-windows-10-using-update-assistant.html
Well it got as far as the restart and said it could take another 90mins.
So I got fed up, came to the pub and left it doing it's thing.
It didn't take that long after the restart.. about half that time or less.