Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.
"Fae" Grace Meadows
Windows File History keeps versioned copies of a user's libraries on a second drive or share. What it covers, where it stops without telling anyone, the Windows 11 and network share setup, and when OneDrive or an image backup is the better call.
A user deletes a spreadsheet on Friday, finds out on Monday, and the first question on the ticket is whether anything on that laptop was ever backed up. Windows has a built-in answer that most people have never turned on and that Microsoft keeps moving around. This guide covers what Windows File History backs up, what it skips without telling anyone, how to set it up on Windows 11 and a network share, and when a technician should recommend it over OneDrive or a real image backup.
File History copies the files in a user's profile to a second drive, keeps every version it sees, and lets you roll back to any of them. It arrived in Windows 8 as the replacement for the old Backup and Restore tool, which Microsoft deprecated at the same time with the note that "its functionality has been replaced by the new File History feature."
The scope is the part to get straight before anything else. Per Microsoft's support page, it backs up the user's libraries (Documents, Pictures, Videos, Music and any custom library) plus Desktop, Contacts and Favorites. That is the whole list. A folder at the root of C:, a second data drive, a line-of-business app's database in ProgramData, Outlook's PST in AppData: none of it is included unless you put it inside a library.
What it does not do is also short. It does not capture Windows itself, installed programs, drivers or settings, so it cannot rebuild a machine. It is a copy of the files a person works on, with history. That is useful, and it is a smaller thing than the word "backup" on the Control Panel suggests.
Windows 11 has no Settings page for File History. Searching Settings for it sends you to the Control Panel, which is where the whole feature lives now: Control Panel, System and Security, "Save backup copies of your files with File History", then Turn on. If no drive is selected, Select drive lists every external disk and lets you add a network location. Windows 10 still has the friendlier route under Settings, Update and Security, Backup, with an "Add a folder" button that Windows 11 removed.
That removal is the change that trips people. On Windows 11 the only way to include a folder outside the defaults is to add it to a library: right-click the folder in File Explorer, Show more options, Include in library. Create a new library for a data drive if you do not want to mix it into Documents. The thread below is from the week Windows 11 shipped, and the complaint in it has not changed since.
Advanced settings, on the left of the same Control Panel page, holds the two values worth changing. "Save copies of files" runs every hour by default and can be set anywhere from every 10 minutes to daily. "Keep saved versions" defaults to Forever, which on a shared office drive means it fills until someone notices. "Until space is needed" is the sane setting for a drive that does nothing else. Exclude folders is on the same page, and Run now forces a pass so you can check the destination before you walk away.
The walkthrough below covers the Windows 11 setup end to end, including the library trick.
File History has no alerting. When the external drive is unplugged, the share is unreachable or the destination is full, it stops, and the only sign is a line in the Control Panel that most users will never open. The feature's own status message, "Reconnect your drive", appears after the destination has been missing for a while. Nothing appears on the desktop, nothing in the Action Center, nothing in an email to anyone.
A technician setting it up for a client ran into exactly that question, and the replies are a fair summary of six years of experience with the tool: good for pulling back a deleted or overwritten file, awkward for restoring to a different machine, and quiet when it stops.
The quiet-failure problem got a public demonstration in September 2026. Microsoft's own security updates for that month broke File History on Windows 10 and Windows 11, with the "Reconnect your drive" message showing on machines whose drive was connected and working, the Last Backup time frozen, and restored files reporting "No previous version available". BleepingComputer reported the fix on 24 September 2026 as optional updates KB5124010 for Windows 11 24H2 and 25H2 and KB5124006 for 26H1, rolling into the October Patch Tuesday for everyone else. Users on the Microsoft forums were still reporting the frozen timestamp after installing it, so check the destination folder's newest file, not the status line.
Four more limits belong on the same list. It copies files, so a file encrypted by ransomware gets copied too, and the only thing that saves you is an older version that the "Keep saved versions" setting has not yet pruned. A drive that is always plugged in is a drive the ransomware can reach. It cannot back up a file that another program holds open in a way it does not like, which is why database files and some mail stores never appear. And it is per user per machine: a second account on the same laptop has its own File History, its own drive selection and its own gap.
The one configuration that makes File History worth a technician's time is a network destination. Point every machine at a share on a NAS or a server, and the office gets one place to look instead of a drawer of USB drives. In Select drive, choose Add network location and give it the UNC path. If the share needs credentials that differ from the Windows login, map it first so the saved credential exists; our guide to mapping a network drive covers the GPO route for a fleet.
On the share, File History creates a tree of FileHistory\<user>\<computer>\Data\ and copies each file under it with the version timestamp appended to the name. Give each user write access to their own branch and nobody read access to anyone else's, because the copies are plain files with no encryption of their own. Use NTFS on the destination if you have the choice; the notes in our exFAT vs NTFS guide explain why FAT-family drives lose the permissions.
Monitoring is the part you have to build yourself. The Control Panel shows "Files last copied on" per machine, which nobody will check across twenty PCs. The reliable signal is the newest file timestamp under each machine's folder on the share: if it is older than a day, that machine's backup has stopped, whatever the status line says. A scheduled script that reads those timestamps and writes the stale ones to a ticket is a morning's work. If you run OpenFrame, that same check is one script run across a client's devices with the output collected in one place.
Four Microsoft features and one category of third-party tool get called "backup" on a Windows PC, and they protect different things. The table is the short version.
| File History | OneDrive Known Folder Move | Windows Backup app | Backup and Restore (Windows 7) | Image backup (third-party) | |
|---|---|---|---|---|---|
| What it covers | Libraries, Desktop, Contacts, Favorites | Desktop, Documents, Pictures | Known folders, settings, app list, credentials | Any folders plus a system image | Whole disk, bootable |
| Where it goes | Second drive or share you own | Microsoft's cloud | OneDrive and your Microsoft account | Second drive or share | Second drive, NAS or cloud |
| Versions | Every change, kept per the retention setting | 30 days of version history | Via OneDrive | Scheduled snapshots | Per schedule, with retention |
| Survives a dead disk | Yes, files only | Yes, files only | Files only; settings restore to a new PC | Yes, including the OS | Yes, including the OS |
| Account needed | None | Microsoft or work account | Personal Microsoft account only | None | None |
| Status | Current, Control Panel only | Current, policy-driven | Current, consumer-facing | Deprecated since Windows 8 | Current |
Two rows carry the decision. OneDrive's version history is retained for 30 days, so a bad edit found in week five is gone, where File History keeps versions as long as the retention setting allows. And the Windows Backup app needs a personal Microsoft account, per Microsoft's own page, which rules it out on any machine signed in with a work account. For a business tenant, Known Folder Move is the one Microsoft recommends and the one you can enforce by policy.
None of the four Microsoft options is a system backup. Backup and Restore (Windows 7) can still make a system image, but it has not been updated since 2012 and Microsoft's guidance is to use a third-party tool. Our disk imaging guide covers what that looks like in practice.
File History is the right call for a narrow case: a single machine, files that live only on that machine, a second drive that stays connected, and a user who can be shown "Restore previous versions" once. A home office, a receptionist's PC that is not on the tenant, a lab machine with local data. In that case it costs nothing, runs hourly, and gives the user a version history that OneDrive's 30 days does not.
It is the wrong call for anything a business depends on. No alerting, no central view, no system image and no protection from a drive that is always plugged in means it cannot be the plan on its own. For a managed fleet, the order is OneDrive Known Folder Move for the user files, an image backup for the servers and any machine that would take a day to rebuild, and File History only as a local version layer on top if someone wants it. The structure of that plan, with the 3-2-1 rule applied to a small office, is in our data backup plan guide.
One more use is legitimate: a stopgap. A new client with nothing in place can have File History pointed at a NAS on every PC in an afternoon, which buys versioned copies while the backup solution is chosen and rolled out. Just put a date on it, because stopgaps that work tend to become the plan.
File History is a versioned copy of a user's libraries to a second drive, nothing more and nothing less. Turn it on through the Control Panel, include extra folders through libraries, point it at a share if the office has one, and watch the file timestamps rather than the status line. Then put a real backup behind it. If you are choosing that layer, start with the backup software comparison for Windows endpoints and servers.
Lead AI Fairy
Some things defy easy explanation: magic dust, the northern lights… and Flamingo’s AI Angels. Think Charlie’s Angels, reimagined with automation brains and serious RMM (Remote Monitoring & Management) chops. Weird? A little. Effective? Absolutely. That’s the job.
Still deciding?
Ask Mingo answers from our docs and customer stories.
Still deciding?
Ask Mingo answers from our docs and customer stories.