Hello
I'm working with Windows 10 Home, 19042.1023 now, (but it was the same some updates before)and with FreeFileSync 11.10.
I had data set up on an external drive I and fileHistory there, but turned off the file version history.
Then I connected a new external plate G. This was recognized both by explorer, and also recognized as a drive on which the file history could have been set up (control panel / system and security / drive select).
Data was available on drive I, but not on G.
Then, with the help of your program, I copied the data from I to G, namely I to G synchronize (mirror) with the filter: except \System Volume Information\ and \FileHistory.
The transfer went perfectly, but: The disk G was no longer recognized for the control panel/FileHistory.
What can I do?
Problems regarding FileHistory
- Posts: 1
- Joined: 2 Jun 2021
- Posts: 1202
- Joined: 8 May 2006
Could you explain that further?
I can find Control | System and Security, but I'm not sure about "drive select"?
Are you speaking of System Volume Information (SystemPropertiesProtection.exe)?
(I don't use it, generally, but) if that is it, if you turned that off, wouldn't it wipe out existing data (restore points & or file versioning)?
Further, I'd have no idea how FFS would handle it?
(\System Volume Information\ is excluded by default in FFS.)
Otherwise, is G: recognized as expected? You can copy files to & from & explore & ... And it shows up as expected in Disk Management?
One possibility, & I'm only surmising, is that I: was seen as a "fixed" device (drive), where G: is (now) seen as a "removable" device (drive)? Maybe that makes a difference?
I can find Control | System and Security, but I'm not sure about "drive select"?
Are you speaking of System Volume Information (SystemPropertiesProtection.exe)?
(I don't use it, generally, but) if that is it, if you turned that off, wouldn't it wipe out existing data (restore points & or file versioning)?
Further, I'd have no idea how FFS would handle it?
(\System Volume Information\ is excluded by default in FFS.)
Otherwise, is G: recognized as expected? You can copy files to & from & explore & ... And it shows up as expected in Disk Management?
One possibility, & I'm only surmising, is that I: was seen as a "fixed" device (drive), where G: is (now) seen as a "removable" device (drive)? Maybe that makes a difference?
