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 No comments

55 answers

Sort by: Most helpful
  1. 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 No comments
  2. 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 No comments
  3. 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 No comments
  4. Virginia M 42,075 Reputation points Independent Advisor
    2020-06-24T13:43:25+00:00

    Unfortunately the only information I can find is either your posts or post pertaining to explorer.exe error with that message.

    It’s certainly puzzling.

    I would suspect this is a 2004 problem. Can you still roll back or is it too late?

    If too late you could try an in-place repair:

    I recommend an in-place upgrade repair.

    To repair Windows without losing any data then follow the instruction here:

    https://www.tenforums.com/tutorials/16397-repai...

    This will also upgrade you to the latest version of Windows - currently 2004 - if you’re not already running this..

    In a nutshell you just download the media creation tool, run this & choose to upgrade now or if you are creating media on another PC you download the tool, run it & choose to create a USB or CD then insert the Windows 10 media (USB/DVD) in the problem PC & run setup from within Windows.

    Please note a repair install is not a reset, this is a last attempt at repairing a PC without a clean install. If this fails to repair the problem then usually a clean install is required.

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-06-24T13:38:53+00:00

    I was actually using two different NAS locations for each machine.

    I also just now tried to use a local disk on one of the machines and it too produces the same error after a clean install. 😞

    Was this answer helpful?

    0 comments No comments