Algunas personas no pueden esperar por una nueva versión de Windows 10. Se registran en Insider Editions y esperan la próxima versión.
I am the exact opposite of that.
I wait and make sure that the version of Windows 10 I'm using is fully compatible with my apps and that I have time to deal with any side effects. My philosophy with security updates is the same; I don't install them right away. (Though I install them every month without fail.) If you haven't installed the January updates yet, please do so as soon as possible.
The main update I mentioned last month was KB4535680, which was offered up to Windows Server 2012 x64 bit; Windows Server 2012 R2 x64 bit; Windows 8.1 x64 bits; Windows Server 2016 x64 bits; Windows Server 2019 x64 bits; Windows 10, version 1607 x64 bit; Windows 10; 1803 x64 bit version; Windows 10, version 1809 x64 bit; and Windows 10 systems, version 1909 x64 bits.
Specifically, for server administrators who control patches on a HyperV server, I recommend that they either temporarily power off virtual machines hosted on that server before installing this update, or skip this update entirely. Even if you are not a server administrator, you may experience problems with this update. In some cases, it may not be offered because it is locked by your original equipment manufacturer. In these cases, the OEM company probably detected that your machine does not have the correct BIOS or firmware to support this Secure Boot update and therefore worked with Microsoft to postpone it.
In some cases, it has been offered to systems that don't support Secure Boot, as Gunther Born noted on his blog. In this case, I recommend skipping this update. On other Windows 8.1 systems, the update installation failed multiple times with an error message indicating problems with the OEM partition. In an answer forum post, several users indicated that they were unable to install the update. If you are in the same boat on the older platform like Windows 8.1, then I suggest you use this Windows Update technique to hide the update.
Some proofreaders were asked to enter a Bitlocker recovery key, even though they did not remember enabling Bitlocker on their computer. In this case, they may find that the system has automatically registered the Bitlocker key to their Microsoft account. If it's not there, there's no easy way to recover a system and you're faced with a rebuild. While these issues are not widespread, the risk of attack against home users is low enough that we recommend hiding this update on older platforms. In Windows 10, the only way to hide it is to use third-party tools or use Microsoft's driver hiding tool, such as wushowhide. This is one of the reasons why I always recommend that you have a backup before installing updates. It not only protects you from ransomware but also ensures that you can recover from any problems.
In cases where I've installed the January updates on Windows 10 20H2 and 2004 hardware, I've found that multiple computers need a second reboot to show the update installed correctly. So don't worry if your systems need a second reboot. If you already installed KB4535680, you don't need to uninstall it; no side effects were observed once the patch was installed.
Recently, an NTFS data corruption bug grabbed the headlines. Microsoft plans to fix the bug, which makes Windows think it needs to fix drive corruption when you inadvertently click an activation file. Independent researchers have developed a tool to protect systems from this bug. As stated on the attackerkb.com website, “The disk is not really damaged. If you try to access the files on the drive, you can still interact with them and do things normally without any problem. Windows just thinks the drive is bad, even if it isn't. " I recommend that you take no action at this time or use the workaround tool. I haven't seen the NTFS bug attack used in the wild; it is safer to be aware of the situation. (As a general rule, be careful when clicking, downloading, or opening attachments. Only open the items you expect or you can be sure they are not malicious.)
One solution we haven't seen, and apparently won't see for a few weeks, is one that removes Flash from systems. This update will not be mandatory until later this year. Until then, if you want to remove Flash, you can manually download KB4577586 from the Microsoft catalog site and install it. I have an explanatory video that you can watch on Youtube. (Adobe began blocking Flash content from running in Flash Player on January 12.)
Silent patches often have the biggest impact on Windows. Google's Microsoft Edge and Chrome browsers recently received updates that can check your saved passwords to make sure they're not weak or included in password breaches. Having said that, I don't recommend saving passwords in your browser at all; instead, I recommend using a third-party password manager tool to save and track your strong, long passphrases. Always remember to add two-factor authentication whenever you can.
Reminder: We are counting down the support window for Windows 10 1909. Windows 10 Home and Professional will end support on May 11. Included in the preview update for 1909 and next month's update will be a notification letting you know when your device is close to that date. After May 11, your device will no longer receive important quality and security updates. (Windows 10 Enterprise and Education editions have an extra year before 1909 is no longer supported.) If you're still running Windows 10 Pro version 1909, it's time to start planning your move to 2004 or 20H2.
Need help upgrading or downgrading to 2004 or 20H2?
<p>Copyright © 2021 IDG Communications, Inc.</p>