Windows 10: Windows 10 Update March 31 2017

Just to add to this story...
Although I was getting an update notification for Defender quite often, i.e. at least a couple of times each day, it's been more than 24 hours now that I haven't got one...maybe a coincidence...maybe MS is trying to resolve it and in the meantime they don't push updates. I don't know!

 

Hi all,

I work for the Windows Defender team (evidenced here: Microsoft Community). I would like to collect some logs from people who have been recently running into the 0x80070643 error. If you are running into this error in the past few days, please kindly send me a PM.

Thank You.

 

@miklet Hi miklet, I didn't explain properly, sorry. I also agree you, unlikely (theory too) it's NOT to do with Creators update. I simply wanted to posit the thought that if MS seem incapable of solving this after now going on four days, how on earth can they have the technical knowledge to produce a bug free functional big update, which I assume is complex, and requires real professionals. I hope it's an optional upgrade. Lazily I haven't looked into that. Any one know?

2. Update on situation here in Japan - on all three desktops, 969x1 and 970x2. It's rougly 1:20pm Japan time. (Ny or about 13 hours behind from memory).

So, all three PCs seem to have a temporary fix. WU no longer checks for Defender updates. Defender definitions always say up to date although over a day old. My last definition is 1.239.603. It's 28 hours old but says up to date.
WU works flawlessly now - except for no definition updates.

In light of the millions who probably are totally at a loss this is a good work around. But it does mean definitions are out of date. The longer the fix takes, the worse the security for Defender. Of course, it's better than nothing.

I am so glad I have a second tandem (Malwarbytes vs 2 (new vs 3 is bugged) running real time, updating hourly and scanning daily. I personally have no security worries for now, and no inconvenience due to this far from ideal temporary fix.

I want to clarify that before posting anything I double check on all three PCs to be sure - Oh my wifes lappy too - same. But there seems to be a variety of oddities so this may not be the case for everyone. I don't know if it's regional, or what, but I'm sure it's not just me. That's all I have for now. Will update when anything changes.

Thanks again to all who have posted in this thread. IMO this kind of info sharing is very useful, and also relieving as it's clear this is a world wide issue with some kind of MS screw up. Security - not good.
Whatever thanks all.

 

Should have included in my previous post. This sounds like what I am experiencing. No notifications at all, in with detail in my above post. Thanks

 

It's still broken. Just got the 'Retry' with the Monday morning definitions and had to install using Windows Defender again. I'm not a beta tester so I'm not going to 'get logs' or whatever. Here's hoping they get this mess fixed soon...

 

I agree that you shouldn't gather info for them. They should be able to 'create' the problem themselves. Surely MS uses their own products and would be able to detect this themselves but it does make you wonder sometimes!

 

Yes this did not fix the problem. Relieved a Definition update this am and got this:





Ugly, Ugly

 

With all the 'telemetry' they collect you'd think they'd have all the info they'd need.

So now with this latest problem my super Windows10 computer doesn't install definition updates and system restore still doesn't work since they broke it in Jan. At least they fixed the video player problem last month within a week or two but come on, this is getting ridiculous. Isn't this stuff supposed to work when it goes into general release? I am not looking forward to the 'creator's update'.

 

Still broken here on the East Coast (USA) in Pennsylvania this morning - 3 April, 2017. Been going on for a number of days. Definition update Error 0x80070643 as others gave posted. Once again I had to install the update thru Windows Defender itself. Glad to have found this thread as I've exhausted all of the ways of trying to fix it without success.

 

It's still down...now 9.35am Toronto time. There were no Definition Updates yesterday so it seemed like everything was ok. This morning, same problem.

Update Defender manually, then Windows Update will be up-to-date.

Hope mS fixes this nuisance soon...

 

Still broke here in Texas also. I made a shortcut to the manual update files and just updated to .701.

C.B.

 

Grrrr. It's back again, same as before on ALL pc's double checked. Incredible! The time to fix I mean.
Already mentioned by JSHERIDON, above, but needs to be said again and again. What the heck is the telemetry for if it can't lead to finding a pattern and making a quick fix for this seemingly one issue.

The MS Security guy from MS is brave to post here, but... What!! Don't they have a few hundred test PCs around the world - they will have been affected. Worst of all, is all the telemetry of any use for trouble shooting such issues. Security is important right? ( I know I'm repeating myself but it's so silly can't help repeating) Why add telemetry (which annoyed many) if it's not even able to clearly form a pattern of this so it can be quickly solved.

Honestly, this is really bad IMO. A quick solution and most people wouldn't have even noticed. But MS looks incompetent now. That's the problem with monopolies - they can get away with this nonsense.

 

I meant to quote you in my last post, but forgot. Any way quoted, and full agree with your opinion. Thanks.

 

It broke on W10 AU for me around the end of March. I installed W10 CU hoping it would go away but no. Under CU updating within WD causes the same error so that workaround is no good. However, downloading the definitions and running the program does update the definitions.

Another issue I've noticed in CU. I get the red message in the Windows Update Screen that some options are hidden by my organization. That was a bug in the CU preview versions that was fixed. It appears that in using Winaero Tweaking program some option or two is the cause of the red message. So keep away from these sort of programs until a CU version is released.

Located in New Jersey USA

 

Thank you. *Smile