From: nospam@needed.invalid   
      
   On Fri, 12/5/2025 10:59 AM, knuttle wrote:   
   > Windows 11 i7 Ultra CPU, 16GB of ram.  No hacks to the system   
   >   
   > I have an external 1TB drive connected to the desktop.  I set up   
   > File History sharing to back up to this external drive.   
   >   
   > However it is not backing up and the error code is that the drive   
   > is disconnected, yet I can access from the desktop that it is connected to.   
   >   
   > How do I reconnect the external drive to File History?   
      
   The drive identifier does not match what was connected at time of setup.   
      
   C:\Users\Paul\AppData\Local\Microsoft\Windows\FileHistory\Configuration   
        Config1.xml         3768 bytes   
      
        
       BAKER   
       D:\   
       \\?\Volume{00117126-0000-0000-0000-1000000   
   0000}\   
       FIXED   
       Paul\WALLACE\Configuration\Config1.xml   
       Paul\WALLACE\Configuration\Config2.xml   
       Paul\WALLACE\Configuration\Catalog1.edb<   
   TargetCatalogPath1>   
       Paul\WALLACE\Configuration\Catalog2.edb<   
   TargetCatalogPath2>   
       Paul\WALLACE\Data   
       98   
        
      
   In a terminal window, I can run "mountvol" and see what my   
   current identifiers are. A person using a USB stick might see   
   a similar "short" kind of identity.   
      
       \\?\Volume{00117126-0000-0000-0000-100000000000}\   
           D:\   
      
   And that allows me to compare to the setting, by using the mountvol.   
      
   You will notice my C: drive has a "richer" identifier of a GPT disk.   
   Disks partitioned as MSDOS, use the shorter legacy identifiers.   
      
       \\?\Volume{0bd6166a-0836-4041-891c-792df2c72abd}\   
           C:\   
      
   The disk drive itself, BAKER partition, has a FileHistory directory   
   and the Config1.xml should be a copy of this same configuration information.   
      
   On the drive that refuses to connect, open its Config1.xml and have a look.   
   Since I just set this up, of course mine matches so this example does   
   not expose brokenness. On the drive you've connected (that refuses   
   to identify), this file will be a mis-match.   
      
   D:\FileHistory\Paul\WALLACE\Configuration   
        Config1.xml         3768 bytes   
      
      
       BAKER   
       D:\   
       \\?\Volume{00117126-0000-0000-0000-1000000   
   0000}\   
       FIXED   
       Paul\WALLACE\Configuration\Config1.xml   
       Paul\WALLACE\Configuration\Config2.xml   
       Paul\WALLACE\Configuration\Catalog1.edb<   
   TargetCatalogPath1>   
       Paul\WALLACE\Configuration\Catalog2.edb<   
   TargetCatalogPath2>   
       Paul\WALLACE\Data   
       98   
        
      
   You can use the settings of the File History control panel to "Add a drive"   
   or whatever.   
      
   I did not particularly see a Registry dependency here. It seems   
   to be using the file systems for this activity, as near as I can tell.   
      
   Since there are also .edb JetBlue databases in each of these directories   
   that hold configuration data, there could be repeats of what is in the XML,   
   inslde the .edb . A naive edit of the .xml file may not be sufficient   
   to "force the identifiers to match".   
      
   But anyway, you can now at least check and see what the name of the   
   partition is, where the File History was supposed to go. It is going to   
   use the Target info in this file, to sniff for the drive.   
      
   C:\Users\Paul\AppData\Local\Microsoft\Windows\FileHistory\Configuration   
        Config1.xml         3768 bytes   
      
       Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)