Discussion in 'other software & services' started by Daveski17, Nov 12, 2014.
As I understand it now, the monthly rollups are cumulative, so you get all the prior KB's. If you are behind on updates and haven't installed March or April, you could be hurting.
As Woody said, "Microsoft released this patch on March 14, without describing its genesis. On April 14, Shadow Brokers released the exploits. By April 24, it became apparent that the EternalBlue exploit was being used to infect normal machines. Prior to that, there was some doubt as to how many machines were infected, and whether the infections were geared toward non-military-grade targets."
Woody Leonhard @woodyleonhard
How to make sure you won’t get hit by WannaCry/WannaCrypt. Step by step instructions to get MS17-010 installed. http://AskWoody.com
"The UK blogger who discovered a 'kill switch' that has slowed the spread of a virus wreaking havoc across the globe has revealed that the world is facing a fresh cyber attack from malicious hackers who are trying to sabotage the fix.
The 22-year-old 'accidental hero' - who lives at home in the south of England with his mother and father - spotted a loophole in the code that meant he could block the virus.
He says he inadvertently halted the ransomware just hours after hearing news of a cyber attack on the NHS while out for lunch with a friend while on a week off from his job at an information security company."
MS-DEFCON 3: Get patched and brace yourself for a Malware-as-a-Service future - AskWoody.
I received Windows Malicious Software Removal Tool (KB890830) this morning on my Win10 x64 CU machines.
Yeah.... I got that one again today too, but on my Win 7 machine. Weird.....
Yeah, but I posted before your post.
Krusty, Tuesday at 9:50 AM
anon, Tuesday at 1:34 PM
Last edited: Wednesday at 3:37 AM
My link it's not just an announcement of MRT update but also explains the reason for the out of band MRT update.
OK, fair enough. Thanks anon!
Nice surprise today.
Microsoft seems to have cleaned up the broken supersedence chain.
It did take a while, but finally, the long superseded KB2987107 (October 14, 2014) is no longer offered.
Wierd issue with Win 10 cumulative update KB4020102 on my secondary computer.
Build is updated to 322, but Update History shows it failed. And on every restart I get the old 'Working on updates - nn% complete - Don't turn off your computer'.
WU troubleshooter does not fix he problem. And uninstalling the KB is unsuccessful.
Tried instead downloading from catalog and get this when running the .msu: 'This update is not applicable to your computer'!
Will try restoring image and try WU again, else just have to hope that a subsequent cumulative update fixes this. But the 'Working on updates' every restart is a PITA.
Edit: Restored an image, tried again with VS and ZAL disabled, same result.
2017-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4020102) successfully installed on 2 machines.
@paulderdash I would also try restoring an image...
@Osaban See my edit above. Primary machine was fine, but different software.
I'm on the LTS version, no update churn on Windows 10.
Nothing to break.
Yes, it's pretty weird, try to hide the update, see this:
Speaking of hardware drivers, if hardware works, no need to update them.
On my venerable HP business machine, I'm still running hardware drivers made for Windows Vista.
They need to be upgraded, why exactly?? Hardware isn't like software. Nowhere close.
Some driver updates fix security vulnerabilties.
For instance, quite frequently, vulnerabilties are found in NVIDIA drivers, and patched with driver updates. Luckily, most vulnerabilties that are found in NVIDIA drivers can only be exploited with local access (AV:L).
Almost no one exploits hardware driver vulnerabilities and as long as it runs its usual to stay with supplied drivers for the hardware's
expected life cycle.
Thanks @Osaban for reminding me about this. Tried it, unfortunately KB4020102 doesn't appear under 'Hide updates'.
I will try image restore once more, else just live with the 'Working on updates' on restarts, and hope a future cumulative update fixes this. Like I said, the build is updated to 332, but the update says failed. Weird. The machine otherwise seems to have no problems.
Which app will you use for the restore? Macrium? Rapid delta restore?
Yep, Macrium. But I only have the free version on that machine, so I guess no RDR? It will be a differential restore just prior to KB4020102 being offered.
I have found my problem. It was RansomOff beta, now temporarily uninstalled. See: https://www.wilderssecurity.com/threads/ransomoff-4.393013/page-18#post-2680569
I have learned over the years that too many layers create more problems than they can possibly prevent. It's good to know you've solved your problem...