home.social

#filehistory — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #filehistory, aggregated by home.social.

fetched live
  1. Discover how the recent September update caused a critical Windows File History bug. Learn about backup failures and how to protect your essential data now.

    #Windows11 #Windows10 #FileHistory #BugFix #MicrosoftUpdate

    securityonline.info/windows-fi

  2. Microsoft Updates Disrupt File History Backup Feature in Windows

    Beware: the latest September 2026 Windows security updates may have an unexpected side effect - disrupting the File History backup feature and leaving you unable to create or update your backups. If you rely on File History, you may want to hold off on installing these updates until the issue is resolved.

    osintsights.com/microsoft-upda

    #Windows #FileHistory #BackupFeature #MicrosoftUpdates #EmergingThreats

  3. Microsoft Releases KB5120249 Update to Fix Security Vulnerabilities

    Microsoft just dropped a crucial update, KB5120249, for Windows 10 versions 22H2 and 21H2, squashing security vulnerabilities and pesky bugs that could compromise your system. This August 2026 cumulative update tackles major issues like File History backup failures and expands Secure Boot certificate coverage.

    osintsights.com/microsoft-rele

    #Windows10 #Kb5120249 #FileHistory #SecureBoot #ServerMessageBlockSmb

  4. Windows 11 users, safeguard your data! Learn how to utilize the built-in File History feature to restore previous versions of your files. It's a simple yet powerful way to recover lost or damaged documents and photos. Protect your work and memories. #Windows #Tech #FileHistory #Backup geekrewind.com/how-to-restore-

  5. Windows is, sadly, still much more generally approachable for your average person than Linux and yet... the solution to the File History problem I just ran into on my partner's laptop was to edit some random binary values into the registry, which somebody discovered by tracing the failure in a debugger. Mad props to "CDub".

    learn.microsoft.com/en-au/answ

    #Windows #Backup #FileHistory #YearOfTheLinuxDesktop

  6. File History does not replace a full backup.

    File history is not a replacement for system image backup If for example your entire hard drive fails It's your system image backup that will allow you to restore your system

    askleo.com/164161 article #164161

    #FileHistory #Windows11Backup #FileBackup #DataProtection #WindowsTips #BackupStrategy #FileSafety #TechTips #DataSecurity #WindowsControlPanel #ExternalDriveBackup #BackupEssentials #ImageBackup #ComputerSafety #MicrosoftWindows

  7. "🛡️ Windows File History Service Flaw: Privilege Escalation Alert! 🛡️"

    A recently discovered flaw in Windows's File History service can be exploited by threat actors to escalate privileges. Microsoft has already released patches, so update now! 🛠️🔒

    A critical security vulnerability has been discovered in the Windows File History Service (FHSVC.DLL), which can be exploited by local users to gain elevated privileges on the Windows operating system. This vulnerability was identified by an independent security researcher in collaboration with SSD Secure Disclosure and was recognized as one of the winners of TyphoonCon's TyphoonPWN 2023 competition in the Windows PE category.

    Vendor Response:
    Microsoft has acknowledged the vulnerability and released a fix, which is available for download from the following link: Microsoft Security Response Center - CVE-2023-35359.

    Technical Analysis:
    The vulnerability resides within the File History Service, which runs with system-level privileges. Local users can initiate the service, and during its startup, a specific vulnerable function within the core file (fhsvc.dll) is triggered. This function, called CManagerThread::QueueBackupForLoggedOnUser, simulates the currently logged-in user and loads fhcfg.dll. This behavior is the root cause of the vulnerability.

    The exploitation process involves the following steps:

    1. Creating a symbolic link of C: pointing to a fake directory (e.g., C:\Users\Public\test).
    2. Leveraging a constructed manifest file (test.manifest) to manipulate the loaded DLL path.
    3. Using a specially crafted second manifest (manifest.manifest) to specify additional dependencies, including msasn1.dll.
    4. Exploiting the msasn1.dll loading process by taking advantage of the file history service's characteristics.

    The vulnerability allows an attacker to escalate privileges from an ordinary user to system privileges, but it doesn't grant the SeIncreaseQuotaPrivilege privilege directly. However, the service does possess the SeImpersonatePrivilege privilege, which can be leveraged to execute a scheduled task with system account privileges.

    🔗 Source: Cyber Security News by Eswar and https://ssd-disclosure.com

    🏷️ Tags: #Windows #FileHistory #PrivilegeEscalation #InfoSec #CyberSecurity

Share on Mastodon

Enter the server where you have an account.