Microsoft backtracks and explains that an annoying bug yet announced as corrected is still relevant. The company has obviously packed a little too early.
The Windows 11 updates cycle is well prowled: when one of them arrives, it corrects bugs, but introduces new ones. It then takes another update to delete them, which leads to others, etc. Okay, we fork the line, but this sequence is not very far from what is really going on. Not this time however, however. Microsoft breaks the monotony with a bug correction which was not one.
After a test update for Windows 11 version 24H2 last June, the KB5060829, Several users find that the operating system firewall made its own. In the file that brings together the events detected by the program, there is a title “Config Read Failed“Accompanied by the message”More data is available“. No need to look for this additional data, there is none, and for good reason: it is a false alert.
Oops, Microsoft announces the correction of a Windows 11 bug by mistake
The Redmond firm has recognized the concern and reassured by saying that it has no impact on the proper functioning of Windows 11. About a month later, it indicates that it is now ancient history. Except that the so-called patch has actually done nothing, supporting testimonies. Nothing surprising at that: it was not expected that he suits anything at this level. To say the opposite was an error.
Microsoft finally added a note explaining that the input concerning the bug “was updated by mistake and classified “resolved” on July 8“The company apologizes and specifies that the fix is still in preparation:“A resolution of this problem is planned in an update that will be published in the coming weeks“In the meantime, don’t forget that if you can ignore the false alert without risk, you have to be careful that it is it that appears before. Do not miss a real warning by mistake.
