Microsoft is among the largest technology companies in the world. The company’s activities in the software field continue actively and it releases new updates for operating systems such as Windows 11.
Windows 11 has been heavily criticized since its first release. In particular, users complain about the operating system due to the errors they encounter. This causes Microsoft to release a new update for Windows 11, and the errors are resolved in these updates. With a recent update, the company fixed an important bug that bothered users.
The system requirements of Windows 11 even forced Microsoft!
It turned out that a Program Manager at Microsoft was using a processor that did not meet the Windows 11 system requirements.
Fixed critical boot error thanks to new Windows 11 update!
Microsoft has recently released a new update for Windows 11 on its website. KB5012643 system during boot, which occurred on some devices with the new update codenamed stuck for 40 minutes Fixed the bug and other bugs that caused it.
With the new update bugs in interface design was also corrected. Problems in the weather and users’ problems with enlarging or shrinking application icons have been largely eliminated. from these errors stuck for 40 minutes It was one of the most boring.
Especially when we come to 2022, it is not appropriate for 40 minutes to pass during the restart. In previous years, people were used to such periods. Due to the weakness of the technology, it took a long time for the parts to act. However, with the new generation technologies, these times have been reduced to seconds.
The frequency of such errors makes Windows 11 unusable. Especially when we look at the user comments, it is said that the errors in the operating system are still very high. This indicates that the operating system is not yet available. In addition to these comments Windows 10 usage Much more compared to Windows 11.
So, what are your thoughts? Do you think the number of errors found in Windows 11 is normal? Do not forget to share your views with us in the comments section or on the SDN Forum.