Daily Gaming news, videos, reviews, tips & guides. Let's share our love of BigN games!

Windows 10: January 2021 It’s time to install fixes

Suffering from minor issues related to the patch bundle that Microsoft released last month, January updates for Windows 10 should be implemented without delay.

Among users, there are those who are interested in installing the most recent version of Windows 10 right now. Some of them sign up for insider cycles and look forward to the most recent version. There are those who want to make sure that the latest version of Windows 10 is fully compatible with their applications and that they have time to deal with any side effects. That is my case. My philosophy is the same with security updates; I do not install them right now (but I do install them successfully every month). If you have not yet installed the January updates, do so soon.

An update under certain conditions

The major security update, announced last month, came with Note KB4535680, Designed for Windows Server 2012 x64-bit systems; 2012 R2 x64-bit; Windows 8.1 x64-bit; Windows Server 2016 x64-bit; 2019 x64-bit; Windows 10, version 1607 x64-bit; 1803 x64-bit version; 1809 x64-bit version and 1909 x64-bit version. For server administrators who are working on pasting the HyperVi server, I recommend temporarily shutting down virtual machines hosted on that server before installing this update – or skip it altogether. Even if you are not a system administrator, you may encounter problems with this KB4535680 update. Sometimes the update is not provided because it was blocked by your device manufacturer. This is if OEM detects that your computer does not have the correct BIOS or firmware to support a secure boot update, and may ask Microsoft to postpone it.

READ  Xiaomi Air charges for wireless charging over several meters, followed by Motorola

Sometimes, as pointed out Gunther Born Sir Son Blog, Which is provided for organizations that do not support secure boot. In this case, I also recommend not using this update. On other Windows 8.1 systems, the update failed again and again with an error message indicating problems with the OEM partition. In one forum, many users pointed out that the update could not be installed. If you are still running an older site like Windows 8.1, I strongly recommend disabling / disabling the Windows update. (See this tutorial in English )

Take a look at bitcoin

Some users who were willing to use the update were asked to provide a BitLocker recovery key – although they do not remember running BitLocker on their computer. If so, they may find that the system has automatically registered the BitLocker key under the Microsoft account. Without this key, it would be difficult to restore a system and they would have to recreate everything. Although these issues are not widespread, I recommend hiding this update on older sites as the risk of attack targeting remote users is high enough. In Windows 10, the only way to hide it is by using third-party tools or using a driver concealment tool from Microsoft. wushowhide.

That’s why I always recommend taking a backup before installing updates. This not only protects you from ransomware, but also allows you to recover your computer in case something goes wrong. When I installed January updates on hardware running on Windows 10 20H2 and 2004, I noticed that many computers needed a second restart to indicate that the update was properly installed. So do not worry if your computers need a second restart. If you have already installed the KB4535680 update, you do not need to uninstall it. I did not see any side effects after installing the patch.

READ  Blizzard: has a new interface!

NTFS error and flash result

Recently, an NTFS data scam caught the headlines. Microsoft plans to fix this error, so Windows hopes to fix the disk corruption if you accidentally click on a file. Independent researchers They have developed a tool to protect systems against this error. As explained website, “The disk is not really corrupted. If you try to access the files on disk, you can keep in touch with them and do things normally without any problems. Windows thinks the driver is corrupted, even if it is not ”. I recommend you do nothing now or use the workaround tool. No attack targeting NTFS error has been reported. You should be aware of the problem. Generally, awareness is required before clicking, downloading or opening links. Open messages and links you expect or only what you know will not be harmful.

A bug that was not included in this update, and will have to wait a few weeks for the Flash to remove the connection from the computers. This update will not be mandatory until the end of the year. In the meantime, if you want to remove Flash, you can manually download Patch KB4577586 Microsoft’s table site Install it. You can watch videos on Youtube Procedures that explain how to do it. (Adobe has blocked the implementation of Flash content in Flash Player since January 12).

Do not ignore browsers and Windows version late 1909

Often, blurred patches have a greater impact on Windows. Microsoft’s Edge and Google’s Chrome browsers have recently received updates that allow you to verify that your saved passwords are strong enough or not used in breach attacks. Passwords. I do not recommend storing passwords in your browser. Instead, I recommend using a password manager to save and test your password strength. Remember to include two-factor authentication whenever possible.

READ  Guam's COVID-19 application alert download rate exceeds state efforts

A final reminder: Support for Windows 10 1909 is nearing its end. Windows 10 Home and Pro versions will no longer be supported until May 11. There will be a preview update for version 1909 and an announcement in next month’s update, which will let you know when your device is out of support date. After May 11, your device will stop receiving security updates. (Windows 10 Enterprise and Education Editions version 1909 is an extra year before retirement). If you’re still using Windows 10 Pro version 1909, it’s time for Windows versions to start migrating to 2004 or 20H2.