how? Having trouble updating Windows 11? Who could have expected that? Well, yes, it happened again. And what’s worse, it happened again with a very important update that puts users in the dilemma of whether to give up what it entails (as we’ll see later) or, on the contrary, succumb to its importance and therefore install it even exposing yourself to possible the harmful effects it can cause.

By mentioning the importance of this update, you probably already deduced it, I’m actually talking about the fix on a Tuesday in Augustyou know, the monthly update released by Microsoft that addresses security issues in Windows 11 (and other versions of the operating system). And the problem is that the simple release of this update can already be used to get “actionable” information about these problems, so its installation is one of the few that should be delayed as long as possible.

Among the other features of this Tuesday patch we will find secure boot enhanced targeting update (SBAT) which aims to resolve the vulnerability (CVE-2022-2601) in GRUB2, one of the most popular Linux bootloaders, a tool often used to configure dual-boot systems, generally Windows and Linux distributions. Of course, these bootloaders play a key role as they are responsible for offering the user access to the desired OS every time the system starts.

Microsoft intended to fix a known issue with this update, but what it did seems to have caused another one. So as we read in Bleeping Computer, August Patch Tuesday for Windows 11 ‘breaks’ dual booting of Windows and multiple Linux distributions. At this point, there have already been affected people who are users of Ubuntu, Linux Mint, Zorin and Puppy Linux, among others. And according to them, since installing this update, they can access Linux because when they try to do so, they get an error message and in some cases even reboot the system.

for now users have found a workaroundconsisting of disabling secure boot, reinstalling the version of Linux affected by the Windows 11 update, including in this process reconfiguring the bootloader, and re-enabling secure boot once this process is complete, otherwise this will also not be possible. access to Windows, given its already more than well-known requirements in this regard.