If File History suddenly says “Reconnect your drive” even though your external disk is connected, don’t assume the drive has died—and don’t erase the backup to test a theory. Microsoft’s September 2026 update notes describe a known File History failure on some Windows devices. The fix status depends on your version: Microsoft says Windows 11 updates released on or after September 22, including KB5124010, resolve the issue; its Windows 10 notes still list the problem without a released resolution as of October 12, 2026. The drive may remain readable even when the backup job fails.

Fast, safe response

Pause repeated “Run now” attempts. Check whether Windows is still writing new backups, protect any irreplaceable files to a separate destination, identify your Windows version and installed update, and avoid deleting File History’s configuration or formatting the disk. The warning is not proof of a failed drive—but an unchanged “Last backup” timestamp means you should treat that backup as stale until verified.

What Microsoft has confirmed

Microsoft lists the same File History symptoms after the September 2026 security update: some people may be unable to create or update backups despite a compatible external or network drive being connected and working. Affected systems may show “Reconnect your drive,” an unchanged “Last Backup” time, or “No previous version available”; Event Viewer may also record crashes involving FileHistory.exe and KERNELBASE.dll. The status is not identical across versions: Windows 11 updates released from September 22, 2026 (such as KB5124010) include a fix, while Microsoft’s Windows 10 update page still lists the issue as unresolved.

That version split matters. If you use Windows 11, first check whether the applicable September 22-or-later cumulative update is installed; it includes Microsoft’s fix. If you use an affected Windows 10 edition, the current support note still says Microsoft is working on a resolution. In either case, preserve the existing history before testing anything: common forum advice such as clearing configuration folders or creating a new backup set can make old versions harder to recover.

What you see What it tells you Safe first step
“Reconnect your drive” while the disk appears in File Explorer Windows may not be completing the File History job; the message alone does not diagnose the hardware Check the drive in Explorer and note the exact warning
“Last Backup” stays at an old date The backup may not be receiving new versions Assume it is stale until a fresh file is verified on the destination
“No previous version available” for files you know were backed up File History may not be reading its catalog or may not have updated it Do not delete the backup folder; test a known file on a separate copy
Event Viewer references FileHistory.exe or KERNELBASE.dll This matches a symptom Microsoft lists for the known issue Record the event time and update history; avoid editing system files
Drive disappears, clicks, disconnects, or reports I/O errors There may also be a physical drive, cable, port, or filesystem problem Stop repeated writes and prioritize copying readable critical files

Step 1: protect the files that matter before troubleshooting

Choose a small set of files you cannot easily replace: current work, family photos, tax or business records, project folders. Copy them—not move them—to another trusted location that is not the same File History destination. That could be a second external drive, a reputable cloud account you already use, or another computer you control. Open a few copied files to make sure the copy is readable.

This is a temporary safety copy, not a full backup strategy. The point is to avoid making a currently uncertain backup your only copy. If the drive is noisy, disconnecting, or generating repeated read errors, minimize further use; repeated scans and backup retries can be unhelpful if a device is physically failing. If the data are valuable and the disk appears damaged, consider qualified recovery help before attempting repairs.

Step 2: distinguish a File History issue from a disconnected drive

  1. Check basic connection. Connect the drive directly to the PC rather than through a loose hub. Try a known-good cable and another port only if the drive behaves normally. A drive letter shown in File Explorer confirms that Windows can see a volume; it does not confirm File History can write a backup.
  2. Check whether files are readable. Browse a few ordinary folders. If Windows asks to format the disk, do not accept that prompt if you need its contents.
  3. Check free space and destination. In File Explorer, right-click the drive and review capacity and free space. If the destination is a network share, confirm the PC can reach the share using the same account that File History uses.
  4. Check the backup time. Open Control Panel → System and Security → File History and look at the last-backup status. Record it before clicking anything. A new date is not enough by itself; later verify that a recently changed file has a fresh copy.
  5. Look for hardware symptoms. A single File History message after an update is different from a drive that vanishes, overheats, makes unusual noises, or triggers operating-system I/O errors.

Step 3: identify your Windows version and update

The Windows 10 and Windows 11 update pages are separate. Press Windows + R, enter winver, and note the version and OS build. Then open Settings → Windows Update → Update history and record the date and Knowledge Base (KB) numbers shown around when the warning started. Do not uninstall anything while still trying to identify the cause.

Microsoft’s notes are version-specific: the Windows 11 page says the File History problem is resolved in updates released on or after September 22, 2026, such as KB5124010; the Windows 10 update page still lists the issue without a resolution. The warning does not mean every Windows computer has the bug. Match your OS version and installed KB to the relevant Microsoft page. If this is a work or school device, ask the administrator before changing updates, drive mappings, or backup policy.

As of October 12, 2026, Microsoft’s Windows 11 notes list a fix in updates from September 22 onward, while the cited Windows 10 update page still says a resolution is being developed. Update notes can change, so check the relevant official page again before applying advice from an older forum thread.

Step 4: verify whether File History is actually creating new versions

Pick one small, non-sensitive test file in a folder included in File History. After the next scheduled backup attempt, check whether a recent version appears through File History’s “Restore personal files” interface. Do not overwrite your working file during this check. If “Last Backup” remains old or no recent version appears, treat File History as not currently protecting new changes, even if the drive is visible.

Keep the test simple and reversible. Don’t rename the backup destination folder, delete its FileHistory directory, clear the configuration, or point File History at an empty disk just to see if the warning goes away. Those steps can create a new backup set while leaving the old history harder to find. If you do not have a verified second copy, preserve the existing destination exactly as it is.

Should you uninstall the September update?

Not as a routine first step. A security update can fix vulnerabilities unrelated to File History, and removing it may expose the PC while failing to restore backups. Microsoft’s notes point Windows 11 users to updates from September 22 onward and continue to list Windows 10 as unresolved. They do not recommend a general rollback as the first fix. If a device is business-managed or the backup contains critical data, get advice from the person responsible for security and backups before changing update state.

Forum posts can help identify a pattern, but they are not universal fix instructions. In a recent Reddit thread, a Windows user described the “Reconnect your drive” warning after an update even with the drive connected. That is useful as a report of what users are seeing—not proof that a particular uninstall, registry edit, or folder reset is safe for your machine. Read the user discussion alongside Microsoft’s official issue note.

What to do next, by Windows version

  • Keep the existing File History disk and its folders intact; do not format or erase them.
  • Maintain a second copy of new, irreplaceable files until a successful backup is confirmed.
  • Windows 11: check Windows Update history for the applicable September 22, 2026 or later update (for example, KB5124010 on supported 24H2/25H2 builds). Install through the normal update path, restart if prompted, then verify a newly backed-up test file.
  • Windows 10: Microsoft’s current notice still lists the File History issue without a fix. Keep a second copy of new important files and recheck the official update page for a status change.
  • Record the date, warning text, Windows version/build, update KB, and whether the drive works in Explorer. These details make a support request more useful.

File History is only one part of recovery. A backup that is always connected under the same Windows login can share some of the risks that affect the PC. Our guide to building a backup plan you can restore from explains why a second, separate copy and an occasional restore test matter. The key question is not simply whether a backup icon says “on”; it is whether you can recover a known file from a copy that the original failure cannot also damage.

When to escalate

Contact your organization’s IT team if this is a work-managed device, the backup destination belongs to an employer, or the files are subject to retention rules. Contact Microsoft support or the drive manufacturer if the device itself disconnects, reports I/O errors, or has unusual mechanical symptoms. If the drive reads normally but File History alone reports the update-matched error, provide the update details and ask whether the known issue applies before authorizing a reset.

If the files are important and the drive contains the only copy of earlier versions, stop destructive troubleshooting. Don’t run cleanup software, format prompts, “repair” commands, or third-party recovery utilities that write to the disk until you understand the risk. A normal-looking backup notification does not guarantee that all historical versions are intact, so verify the files you may need before you depend on them.

FAQ

Does “Reconnect your drive” mean my external drive is broken?

No. Microsoft describes a known post-update File History issue that can show the warning when a working compatible drive is connected. Still, check for separate signs of hardware trouble such as disconnects, noises, or read errors.

Can I keep using the computer?

Usually the warning concerns File History, not whether Windows itself can start. But until a recent file version is verified, assume that new edits are not being protected by that backup. Make a separate copy of important work.

Will a new drive fix it?

Not necessarily. Users have reported the message even when the drive can be read. Replacing or formatting the drive before confirming a hardware fault could waste money or make old backups harder to recover.

Is the issue fixed now?

For Windows 11, Microsoft says updates released on or after September 22, 2026 (including KB5124010) resolve it. Its Windows 10 update notes still list the issue without a released resolution as of October 12, 2026. Check the page for your exact version and installed KB.

Where is File History in Windows?

Microsoft describes it under Control Panel → System and Security → File History. The exact search path can vary by Windows build, but you can open Control Panel and search for “File History.”

The takeaway

A post-update “Reconnect your drive” warning is alarming because it sounds like the only backup has disappeared. Microsoft confirmed a September 2026 File History problem that can affect backups even when the drive works. For Windows 11, install the applicable update released from September 22 onward; for Windows 10, keep a separate copy while Microsoft’s listed resolution remains pending. In either case, preserve old history, identify your build and KB, and verify a fresh version by restoring a test file before trusting the backup again.

Sources

End of articleOur method →