Missing files after switching to new drive for boot

JoshBungs said:

no that is incorrect. The F: drive was my Samsung SSD, always listed as such. The drive sizes are also different, so there was a clear distinction as well as a difference in the labelling.

So, according to your OP - you had a HDD, which when it was booting as the only drive was C: drive. Then you cloned it to an SSD, and when you booted Windows from the SSD, the SSD running Windows on it was F: drive. That's quite a cloning program that would change all the registry entries required to run Windows from F: drive. In normal circumstances, as @CountMike points out, when Windows loads, the partition containing that Windows system is C: drive. Load Windows on drive 0 - it gets C: and drive 1 will get a different letter. Load Windows on drive 1 - it gets C: and drive 0 will get a different letter.

I have yet to see a cloning program that will clone a Windows partition and make all the changes to the Windows registry to change it's drive letter to make it get something other than C: drive when booted into.

CountMike said:

You said that "now the SSD has been renamed to C:" so I suspect your cloning did not go thru well. Whichever disk/partition you BOOT from Windows labels C:\. It's possible that all this time you had both disks in, it was BOOTing from one disk but running Windows from another one.

I suspect that is probably correct. But doesn't explain the missing documents or document folders that were saved specifically to the SSD

NavyLCDR said:

So, according to your OP - you had a HDD, which when it was booting as the only drive was C: drive. Then you cloned it to an SSD, and when you booted Windows from the SSD, the SSD running Windows on it was F: drive. That's quite a cloning program that would change all the registry entries required to run Windows from F: drive. In normal circumstances, as @CountMike points out, when Windows loads, the partition containing that Windows system is C: drive. Load Windows on drive 0 - it gets C: and drive 1 will get a different letter. Load Windows on drive 1 - it gets C: and drive 0 will get a different letter.

I have yet to see a cloning program that will clone a Windows partition and make all the changes to the Windows registry to change it's drive letter to make it get something other than C: drive when booted into.

it may be that I was incorrect on which drive it was booting from, but the speed seemed to be as such that it was the SSD while the SSD was still labeled F:
I had manually changed the boot order to prioritize the F: drive to boot from. But I may be incorrect. It is probably as CountMike said, it booted from one drive but ran windows from another.
However I am 100% certain F: was my SSD and F: had my newly created documents on it. Now it does not

so it seems there is no solution.
thanks for your time everyone