Beware! This horrible Windows 10 bug has also hit Windows 11

Windows 11 has rolled out a lot of useful new features for users, but unfortunately, along with all that, it has also brought along a handful of bugs. Now, a bug discovered on Windows 10 and older versions has reportedly been spotted on Windows 11 and it could interrupt your workflow.

Check out the Windows 11 bug that has already created quite a bother for users just as it did Windows 10 users earlier. Here’s everything you need to know about the latest Windows 11 bug affecting users. (Pixabay)

Windows 11 launched two weeks ago, but the company's much-awaited upgrade has had its fair share of bugs alongside the useful new features that it offers for users. With the arrival of Windows 11, users with AMD chipsets have been hit by performance drops, while other bugs have also surfaced. The latest Windows 11 bug that is impacting users is the PrintNightmare bug. This is the same Windows 10 bug that caused massive headaches for users before Windows 11 was officially launched.

Microsoft has already patched the vulnerability more than once, but the company has reportedly identified three new issues that affect the system on Windows 11 and on Windows 10, according to a report by Bleeping Computer. The PrintNightmare bug is now causing issues for users who are trying to install a new printer.

Some of the issues faced by users include the inability to add a new printer using an HTTP connection, or while trying to connect to a printer using the Internet Printing Protocol. Similarly, print server clients might not be able to receive custom printing properties, which can also cause issues while printing. These are certainly noteworthy issues that can have a massive impact on companies and corporations, especially those that rely on printing.

According to the report, the following Windows versions are affected by the printer issues: Windows 7 SP1, Windows 8.1, Windows 10 (21H1, 20H2, 2004, 1909, 1809, 1607), Windows 10 Enterprise 2015 LTSB, and Windows 11 21H2. Similarly, Windows Server version 2022 is affected, as are older versions going back to Windows Server 2008 SP2. Unfortunately, at this point, it looks like Windows users will have to wait for a permanent fix as the flaw itself is important enough that Microsoft had to disable specific functionality until it is fully fixed.