Attention! Windows 10 nightmare has arrived in Windows 11!

Windows 10 suffered from several issues, particularly at this late stage. One of the most popular was what happened to printers. Lo and behold, the big Windows 10 nightmare has arrived on Windows 11 and is already causing a lot of headaches. So after installing the KB5006674 update, problems start to print, especially when it comes to network printers.

Attention! Windows 10 nightmare has arrived in Windows 11!

After installing version KB5006674, the following errors appear:


Windows 11 nightmare

Meanwhile, this nightmare, which has now arrived in Windows 11, also includes almost all versions of Microsoft’s operating system. These are Windows 10, version 21H1, Windows 10, version 20H2, Windows 10, version 2004, Windows 10, version 1909, Windows 10, version 1809, Windows 10 Enterprise LTSC 2019, Windows 10, version 1607, Windows 8.1; Windows 7 SP1

For the server version, Windows Server 2022, Windows Server, Version 20H2, Windows Server, Version 2004, Windows Server, Version 1909, Windows Server, Version 1809 and Windows Server 2008 SP2 are affected.

Microsoft is already looking for a solution to this problem.

However, this is not the only problem that is causing a headache in Windows 11 and others. A security researcher has revealed the details of a new threat that, under certain conditions, can give attackers complete control over a system. That means someone, and especially someone you know, can get their hands on your computer. However, this error affects all Windows versions at risk!

Alarm! All Windows versions are in danger! And now?

In the midst of it all, however, there is good news. In order to successfully carry out this attack, the attacker must find out the username and password of the victim. Of course it won’t be difficult for some, but it will be for others.

But when there is good news, there is also bad news. It’s just that no version of Windows gets away from it. In fact, not even the new Windows 11.

Windows 11 nightmare

Microsoft fixed this issue in August, but it didn’t really work out well.

In August, Microsoft fixed a vulnerability that could increase the properties of a user. However, the correction was not enough. So it could still be bypassed in a new exploit that was even published on GitHub.

The security researcher who discovered all of this says that he only fixed the symptom of the reported bug and not the cause as stated on the website. Beeping computer.

Although it is necessary for the attack to know the victim’s username and password, it remains a serious problem.

Microsoft has not yet commented on this case at the time.

Even if problems are fixed, it doesn’t necessarily mean it’s over. It now remains for us to wait for more news on this issue and, in particular, for a fix from Microsoft.

Leave a Comment