Separate names with a comma.
Discussion in 'HardForum Tech News' started by Monkey34, Jan 14, 2020 at 7:32 AM.
WTF no W7? Guess I better upgrade to 10 asap! Well played m$.
Guess this has to be important. Tomorrow's the rollout of the Chromium-based Edge. If this wasn't urgent, they would have just waited a day.
Win7 support officially ended today.
Those outlier machines you handle on a case-by-case basis, but any of the sensitive info lives on the server inside a secure room. If your accountant is keeping financials on a local machine, that accountant is embezzling money.
The servers you update as soon as possible, after hours or as close to after hours as you can manage, with backups at your fingertips.
IP you protect with lawyers.
What a coincidence... couldn't have planned this... unless...
So am I missing something or is this just an exploit that makes an executable not give an extra warning about not having a properly signed certificate?
It seems like this would have to be paired with a remote execution exploit to be very dangerous since if you can convince an idiot to d/l and run something an extra warning usually isn't going to stop them.
Interesting that there is no Win 8.1 update listed. Support for that runs through 2023. Wonder if there will be more additions later.
People - "The vulnerability affects Windows 10 and Windows Server 2016/2019 systems."
win7/8 not affected.
Oh... man... spoiling our great conspiracy theories.
That's very common and achievable with a level 2 & level 1 tech
I would simply find the dism command needed to uninstall the patch, send it to all computers simultaneously and reboot. Or automate with a script if physical access needed to fix. Run script and move on.
But agreed never blindly install patches without reading known issues on MS's site
i'm assuming 1909 doesn't need it?? i'm pretty sure it didn't come up on either of the two 1909 enterprise installations i have here at the house. and if you go to the actual download page for the update it's only showing for the older versions of win10 and 8 & 7. unless i'm missing something.
1909 needs it. I installed it last night.
Windows 10 Version 1909 for x64-based Systems Article: 4528760 Patch: Security Update
Blame the Forbes article which mentions W7 and 8. Guess I shoulda known better, fake news.
"Before you take a deep breath and relax because you're still using Windows 8, Windows 7 or Windows XP, that same crypto component is present in all versions of Windows. "
To the OP, if y
Finally got the update to start. It was stuck pretty good there.
Seems I had installed Spybot Anti-Beacon and forgot about it.
It left comments explaining in my HOSTS file was how I found.
Disabled Anti-Beacon's immunization and rebooted.
Update hasn't finished, but at least its futher than before.
So, when it finishes I turn Anti-Beacon immunization back on?
Or I need an updated anti-beacon? Prolly wouldn't hurt...
MS best not be reinstalling stupid games and whatever other
garbage I've deliberately removed...
So, is this CVE-2020-0601?
How does someone write an article about a vulnerability without referencing the tracking number?