The change often happens very slowly, and in the case of the Windows explorer is ponderous and delayed in the case of OneDrive files, this problem has appeared since the dawn of dinosaurs. But finally, in a compact update of Windows beta, Microsoft apparently solved the problem.
Update in question KB5052094Although this applies only to people from the Windows 11 channel review Windows report). I apply the standard public version, so I was unable to check Microsoft’s claims that it repaired the problem “the context menu slowly after clicking cloud files”.
But I certainly hope that yes, because as long as I apply OneDrive and Windows 11, the delay of interaction slowly driven me up the wall. I understand that changing the name of the cloud -based file cannot be as immediate as doing the same for anything on a local day of SSD disk, but sometimes the delay between clicking “change the name” and the actual possibility of this can pass a second.
Now I am sure that some of you may feel that the real problem is that I apply OneDrive and I will gladly agree with anyone who thinks that this is not the best cloud service. However, I apply it all the time to perform comparative tests of games on many computers, because I have configured testing software so that the results file is saved in my OneDrive. Then I can access those on my main computer while others are still working.
The opening of such files is fine, but making anything contextual menu (e.g. copying, name change, cloning) is quite tiring due to delay. If this amendment really solves this problem, I will be one content person. What puzzles me is why, in hell, it took Microsoft to create and release a solution. I can only assume that he did not think that the error is high enough priority and let’s face the truth, Windows 11 certainly has much more pressed problems than it requires repair.
Either this or the solution concerned changes on Azure servers, and taking into account how costly they are, all changes in what they do or what equipment is used, they are potentially very costly. What may seem like a compact correction at the end of the user may include a whole lot of main corrections on the server side.
In any case, I want the amendment to be publicly implemented as soon as possible. Even if it slightly improves the situation, it will make my professional life much nicer. As long as the next Windows 11 error did not have my runs.
