File History: Element Not Found Error on Windows 10 May 2004

Anonymous
2020-06-22T19:28:01+00:00

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.

0 comments

55 answers

Sort by: Newest
Most helpful Newest Oldest
  1. 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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-25T05:29:40+00:00

    Good news, Time Lady  -- it worked!

    Well, somewhat.  What I ended up doing was:

    1. Stop using drive.
    2. Run repair.
    3. Reconnect drive/rebuild history.

    After this I was able to get the expected functionality.

    The bad news, however, is that now after repairing my Windows 10 install, it has led to another problem altogether, in case any you or anyone would like to assist:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-repair-windows-now-thinks-c-is-d-and-doesnt/34e113ce-f080-4ba1-a9da-64f667038841

    Thanks again for helping troubleshoot this issue!

    Was this answer helpful?

    0 comments
  3. Virginia M 42,075 Reputation points Independent Advisor
    2020-06-24T16:42:34+00:00

    If the repair doesn’t work then unfortunately I’m out of options.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-24T13:51:37+00:00

    Yeah unfortunately it's too late, stuck with 2004 as it is.  As for the drives, the network folders were there but they were not attached/mapped.  That is, I was using network paths and not mapped drives.  The other drive I just now tried was a spare and was not attached.

    I will look into performing this repair but I am not hopeful. :P

    Was this answer helpful?

    0 comments
  5. Virginia M 42,075 Reputation points Independent Advisor
    2020-06-24T13:44:59+00:00

    I’ve just thought of something - did you have any of those drives connected When upgrading to 2004?

    This may be the problem if so.

    You may have to disconnect all USB drives & devices before running the in-place repair.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments