I’ve moved to Macrium Reflect which is also free & is more reliable.
File History: Element Not Found Error on Windows 10 May 2004
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Using Windows 10 May 2004 edition with a brand new install of File History on two different machines now, I have managed to run into the following issue.
Selecting Clean up versions, then "Clean up":
I get the following dialog:
Again, this is on two different machines, with a clean install.
Note that I am using a simple folder with a 4KB file within it, although I first saw this on a fully-configured install with about 1.5TB worth of data within it. This led me to diagnosing the issue and ultimately trying it on these two separate machines with a clean install.
Is this a known issue for 2004?
Thank you for any assistance/context/insight you can provide!
Windows for home | Windows 10 | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
55 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 18%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Virginia M 42,075 Reputation points Independent Advisor2020-11-30T13:45:52+00:00 how does one run an in-place repair
Download the media creation tool & double-click it to run, then choose to upgrade this PC now.
-
Anonymous
2020-11-30T13:39:14+00:00 how does one run an in-place repair
-
Virginia M 42,075 Reputation points Independent Advisor
2020-06-25T12:36:29+00:00 I should update to say that a simple repair did not work. I had to disconnect the drive and then repair. So I effectively repaired twice (which might have led to the other issue I am now facing). There might be other unknown considerations at play, but that's what worked for me.
Glad to hear the repair did work, I mentioned that you may need to remove any drives - which included the file history drive. I’ve found doing this gives the best install of a new version of Windows.
Sorry to hear it caused further problems though.
I see my fellow IA Greg is ansering you on your other question. I’ll take a look though.
-
Anonymous
2020-06-25T05:31:57+00:00 I should update to say that a simple repair did not work. I had to disconnect the drive and then repair. So I effectively repaired twice (which might have led to the other issue I am now facing). There might be other unknown considerations at play, but that's what worked for me.