Are file history records still in use?Protest and appeals against Microsoft's technical support team

KB5101684 and KB5120249 both state that this update fixes an issue that affects File History automatic backups to network shares using Server Message Block (SMB). Backups did not work because Windows displayed a false invalid credentials error when connecting to SMB shares. Fixing this issue leads to the following problems.

File History Issue Symptoms

Affected Systems: Windows 11 25H2 (after installing KB5101684) and Windows 10 22H2 (after installing KB5120249).

Key Anomalies:

Data successfully backs up to the D: drive, but the Last backup timestamp in the Control Panel fails to update.

Newly created or edited files (such as Word documents, images, and videos) display There are no previous versions available under Properties → Previous Versions.

Temporary Workaround: Users must manually navigate to Control Panel → File History → Select drive, re-select, and confirm the D: drive to temporarily restore normal functionality.

Before updating these two, I never deleted system folders, login files, or messed with settings.

Protest and Appeal to the Microsoft Technical Support and Development Teams

To the Microsoft Support and Engineering Teams:

As long-time, loyal users who heavily rely on built-in Windows backup mechanisms, we are profoundly disappointed and frustrated that recent updates—specifically KB5101684 for Windows 11 and KB5120249 for Windows 10—have broken the File History feature, freezing backup timestamps and rendering Previous Version completely useless.

File History is far from being an obsolete or unused feature. For countless professionals, students, and everyday users who prefer or require local data protection as a critical safeguard against file corruption, accidental deletion, and ransomware, this is an essential line of defense. However, after installing official cumulative updates, two entirely independent computers—neither of which had altered system registries or deleted system folders—simultaneously suffered the exact same failure. This proves beyond a doubt that the updates introduced a regression or damaged the underlying sync mechanisms.

What is even more infuriating is:

A Complete Lack of Official Communication: Users facing these update-induced silent failures are left stranded in community forums without any official acknowledgment or explanation from Microsoft.

Ignored Feedback: Detailed reports submitted through the Feedback Hub, complete with cross-computer diagnostic comparisons, have met with radio silence.

We hereby formally demand that the Microsoft technical team:

Acknowledge and Investigate Immediately: Treat the regression caused by KB5101684 and KB5120249 on File History, VSS (Volume Shadow Copy Service), or directory indexing as a high-priority bug and launch an immediate investigation.

Provide a Fix and Clear Transparency: Roll out a definitive patch in the upcoming security or optional updates to resolve the frozen Last backup indicator and broken previous versions, and provide a clear public statement to affected users.

If Microsoft continues to neglect this essential feature or turns a blind eye to its decline, we will have no choice but to continuously escalate this issue through all available official support channels, technical forums, and community networks until this critical bug is thoroughly investigated and resolved.

Since most people use File History, if you have the same issue as me, don't worry, feel free to leave a comment.