Windows 10 Update March 31 2017
-
tomcat, HERE is the link to the manual download. Scroll down.
C.B.
-
-
I sure am glad this forum is here to share this info, otherwise can you imagine the steps we'd be taking to try and fix this mess. Thanks to all for the continuing reports. :)
You're welcome, Sir!
-
tomcat,
HERE is the link to the manual download. Scroll down.
C.B.
Thanks for the link! :)
-
-
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.
-
random thought
So many different build versions experiencing this update phenomena, seems unlikely to me that it is related to the Creators Update and more likely a general Windows Update issue, specifically affecting Defender.
Just a theory
@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.
-
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!
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...
-
-
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!
-
I to started receiving this issue since Friday 31st of March. Got it again this am on 2 systems (HOME and PRO). I too am getting unhappy with ANY Window Update now. Decided to try the Window Update Trouble shooter. I was amazed of what it returned. See below:
Issues found
Some security settings are missing or have been changedSome security settings are missing or have been changed Fixed Fixed
Reset security settings Completed
Service registration is missing or corruptService registration is missing or corrupt Fixed Fixed
Reset service registration Completed
Potential Windows Update Database error detectedPotential Windows Update Database error detected
Possible issues may prevent Windows Update from keeping your system up to date. Fixed Fixed
Repair Windows Update Database Corruption Completed
Windows Update components must be repairedWindows Update components must be repaired
One or more Windows Update components are configured incorrectly. Fixed Fixed
Repair Windows Update components Completed
Potential issues that were checked
Default Windows Update data locations have changedDefault Windows Update data locations have changed
The location where Windows Update stores data has changed and must be repaired. Issue not present
Check for missing or corrupt filesCheck for missing or corrupt files Issue not present
System date and time aren't correctSystem date and time aren't correct Issue not present
Issues found Detection details
6 Some security settings are missing or have been changed Fixed Fixed
Reset security settings Completed
6 Service registration is missing or corrupt Fixed Fixed
Reset service registration Completed
6 Potential Windows Update Database error detected Fixed Fixed
Possible issues may prevent Windows Update from keeping your system up to date.
Repair Windows Update Database Corruption Completed
One troubleshooting step to resolve WU issues is to delete and re-download updates to your computer. would you like to try this step now? Depending on your network configuration, you may incur download costs.
InformationalDataStoreAndWULogFiles.zip
60.22MB
File Name: DataStoreAndWULogFiles.zip
6 Windows Update components must be repaired Fixed Fixed
One or more Windows Update components are configured incorrectly.
Repair Windows Update components Completed
Repairing Windows Update components frequently resolves common Windows Update errors.
Potential issues that were checked Detection details
Default Windows Update data locations have changed Issue not present
The location where Windows Update stores data has changed and must be repaired.
Check for missing or corrupt files Issue not present
System date and time aren't correct Issue not present
Detection details Expand
InformationalNetwork Diagnostics Log
File Name: 87143799-D41C-4C42-98E4-9DE8C745BF86.Diagnose.Admin.0.etl
InformationalNetwork Diagnostics Log
File Name: 27DE9776-C6C6-45C2-B258-C0C0B182C825.Diagnose.Admin.1.etl
InformationalNetwork Diagnostics Log
File Name: 0C46AD76-815C-4FF8-9B70-C833FCD977C8.Diagnose.Admin.2.etl
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
InformationalService Status
Problem with BITS service : The requested service has already been started. More help is available by typing NET HELPMSG 2182.
InformationalService Status
Problem with BITS service : The requested service has already been started. More help is available by typing NET HELPMSG 2182.
InformationalService Status
Problem with BITS service : The requested service has already been started. More help is available by typing NET HELPMSG 2182.
Collection information
Computer Name: DESKTOP-71LLIQU
Windows Version: 10.0
Architecture: x64
Time: Sunday, April 2, 2017 5:20:05 AM
The same report was returned on the other machine. This has to be a one of those "Windows Update" that broke "Windows Update" !
Looks like its fixed, but won't know until another update comes thru.
Yes this did not fix the problem. Relieved a Definition update this am and got this:
Ugly, Ugly