The February cumulative update caused abnormalities in Windows 10’s File History function
Every time Microsoft releases a cumulative update, it fixes old problems and brings new problems at the same time. For example, in last month’s routine update Microsoft fixes a large number of discovered security vulnerabilities.
However, this cumulative update also brings new problems: Windows 10 File History function is abnormal and even causes the backup function to be destroyed.
We also use the file history function, but if we hadn’t seen feedback from other users, we hadn’t noticed that this function has been unable to back up files normally.
The historical file recording function is actually the file backup function provided by Microsoft, which will generate multiple backups of files in the user-specified location according to the point in time.
Therefore, even if the user accidentally deletes or modifies the file, he can easily restore the file through the file history or restore it to a certain point in time.
It seems that the number of users used by this feature is not that many, but if you have sufficient hard disk space, you may wish to turn on this feature to make multiple backups of your files safer.
It’s just that this feature seems to have been broken by the cumulative update released by Microsoft. The actual measurement found that the file history cannot be backed up after installing the cumulative update last month.
At present, some users have given feedback on this issue in the official Microsoft community. Some users can activate this function but cannot back up any files normally.
Some users are directly unable to start this function and therefore cannot be used. Under normal circumstances, this function can be automatically backed up without user intervention afterward.
Although the February cumulative update can be uninstalled, if the user uninstalls the update, it may be exposed to security vulnerabilities.
Therefore, based on security considerations, we do not recommend users to uninstall the cumulative update, but Microsoft has not yet confirmed this issue so it is not clear when it will be fixed.
Via: mspoweruser
