It’s a shame to say it, but the truth is that with Windows 10 2004 Microsoft has had an important stumble. And it is worth, we agree that any change in an operating system can affect many more elements of it than it might seem at first, but precisely for that reason, and before ending and ready to distribute a update of this type, testing should be maximized. And if instead of May Update it should be called June Update or September Update, because in the end it is not so problematic either.
And yes, it is true, the software life cycles are not established arbitrarily, there is a reason for being behind them and modifying a date can translate into a total change in the model followed up to that moment. I get it, of course, but in any case I think that it is better to bear the consequences of making such a change, either in a timely manner or by resetting the entire calendar, which see how the trickle of failures, problems and others, ends up turning Windows 10 2004 into a failed update.
And it is even worse when, despite having reached that point, and with more than a month to live in this new version of the operation, new incidents continue to appear related to the update, and Microsoft has to recognize the error and, in the absence of a definitive solution, offer a method that allows, temporarily, access to the functions affected by the update to Windows 10 2004. An update that, let’s not forget, Microsoft is forcing on some systems.
The problem we are talking about this time affects OnDrive users, who have started reporting that since they upgraded to Windows 10 2004 cannot access the files they have synchronized from the operating system with Microsoft’s cloud storage service. Thus, it is neither possible to back up the files with which they are currently working, nor to recover those files replicated in the service.
And not only is that, to further complicate the situation, it seems that many users not only cannot access the synchronization functions with the cloud, but also find it impossible to open previously downloaded documents, once they carry out the update.
The good news is that Windows troubleshooter can apply the interim procedure designed by Microsoft so that users with Windows 10 2004 can re-access their files in the cloud from the operating system, as well as reactivate their synchronization to keep them safe in the event of a system failure. However, this system does not always work and, in such a case, users will have to carry out a somewhat tedious procedure:
- First you need to open the command prompt console as administrator. To do this, in the search bar you must type CMD and, in the result that will be displayed, right-click (on PC) or a long press (on touch device) and, in the menu that will be displayed, choose the “Run as administrator” entry.
- Once in the console, copy the following text and hit enter: reg add HKLM System CurrentControlSet Services Cldflt instances / f / v DefaultInstance / t REG_SZ / d «CldFlt»
- When the command has been executed and the prompt is active again waiting for a command, close the window and restart the system.
- Now you should verify that OneDrive features are active. To do this, access the client configuration of the service in Windows 10 2004. The way to do this is to locate its icon in the system notification area, right-click (or long press on touch devices) and click Settings.
- Once there, check to see that the client settings have not been changed, and therefore the sync features you commonly use are active, as well as pointing to the correct files and folders.
- If you use more than one OneDrive account, keep in mind that you will have to repeat steps 4 and 5 with each one, to make sure that everything has returned to normal.
This is, as we mentioned before, a workaround until Microsoft releases a patch It will definitely fix Windows 10 2004 problem with OneDrive. Let’s hope that it arrives soon but, above all, let’s hope that it is the last problem attributable to this update, because the list by now is quite excessive.