Esta semana ha traído ciertas actualizaciones que estimo indispensables para los “tres grandes”: mi sistema operativo (Windows), mi navegador (Chrome) y mi teléfono (Apple). Las 3 versiones corrigen las primordiales vulnerabilidades de día cero en las 3 plataformas.
Although I invite you to patch Google Chrome and your iPhone as soon as possible, I invite you not to update Windows. That remains true, at least until we see if there are any trending side effects from the Patch Tuesday updates.
Let's examine the patch to do it immediately.
First, prioritize fixes for Apple devices. Among this week's fixes is one for the Pegasus spyware, which can unlock access to the camera and microphone, such as text messages, phone calls and emails. iPhones, in particular, have come under attack. Apple generally pushes these updates overnight if your phone is plugged in and charging (and connected to the internet). If you want to make sure your iPhone has received the update, click Settings, then General, then tap Software Update. Usually, after my iPhone updates, certain apps may require passcodes again. Personally, I try to save critical items to iCloud Keychain. Check for fixes for iOS 8 and iPad OS 8, and security update 6-XNUMX for macOS Catalina and Big Sur XNUMX.
Google Chrome browser update fixes 2 vulnerabilities in the wild fixed in version 93.0.4577.82 for Windows, Mac and Linux. (For those using Google Chrome OS, Bleeping Computer reports that certain devices reported black screens after attempting to sign in to their Google Chrome OS accounts.)
And finally we come to Microsoft. For anyone hoping that the current month's updates will "fix" an issue related to the use of the Set Policy for printer management in your domain / business users (I wrote about this before), welcome to your new standard: the way incorporating the printers is not fixed. What has been fixed is another stealthy attack that used the spooler to gain more access to their machines. Therefore, we will have to re-incorporate the print drivers by multiple means.
Clearly, Microsoft doesn't see (or supposedly understand) how disruptive this change has been for business users. This may be due in part to the fact that for many companies the impact has been mitigated as employees are out of the office and need to print. But as employees return to the office, we will need to use new techniques to incorporate printers. Policy MVP Jeremy Moskowitz wrote the ultimate solution and advice for this issue. For users with a directly attached printer, there have reportedly been few issues with PrintNightmare's fixes. I did not see any side effects in the month of August and have not seen any so far in the month of September.
If you are still using Windows XNUMX version XNUMX, please note that December XNUMX, XNUMX marks the end of support for this version of the operating system. Although Microsoft has announced the release date of Windows 21 (October 2), it has said little about the arrival of Windows XNUMX XNUMXHXNUMX. Everyone continues to assume it's going to be October, but no one seems to know. (The process of upgrading from 20 to 2H21, or even 1H21, was minor for me; I don't anticipate any downsides for those who want to upgrade to feature version 1HXNUMX.)
We have seen some expected changes discussed on the weblogs, but not when they will be published. Since 21H2 doesn't seem like a major release, I don't expect distributors to have major issues. Normally, it seems to be more of an enterprise version on the way to Windows XNUMX. Given the small number of changes, I would expect to give an "all set to install" in a few months after release.
Microsoft is in the process of releasing 21H2, as well as Windows XNUMX, to commercial vendors so they can ensure their apps work on both versions. Obviously, its release is close as Microsoft returns to produce KB4023057, the update for the components of the Windows XNUMX update service that it releases quarterly. It is used to ensure that computers that are not part of a domain or corporate configuration are ready for the next release of functionality by checking that the Windows update process is correct, that there is enough free disk space for updates, that the network settings are restored if an issue is noticed, and that the Windows update history database is restored if necessary.
Many users rely on the Wumgr tool to hide this update as it has been reported to cause network issues on certain computers. If the patch is already installed, there is no need to uninstall it as the processes have already been performed. Personally, I like to periodically check my system for medical issues, so I make sure to check the C: drive for space issues. If I get error messages when trying to install Windows updates, the best way to fix the system malfunction is not to use the sfc /scannow or DISM commands; I would do a repair install on it. You won't lose any data and your computer will be healthier when you're done.
So when we look at 21H2 and Windows XNUMX, I'm still in test mode for this week's Patch Tuesday arrivals, as I should be too.
<p>Copyright © dos mil veintiuno IDG Communications, Inc.</p>