Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Lucky_Phil

  1. Just for information to others who may have experienced this same issue.

    Since Jan 21 2021 my scheduled tasks ... Duplication and Backup on Windows 10 1909 failed to launch. No errors recorded Retrospect simply failed to auto launch to perform my scheduled Backup and Duplication jobs which it had been doing successfully for years. The only thing I can suggest is that a Windows security update on Jan 21st somehow interfered with the auto launch of Retrospect on my PC.


    The Retrospect services Retrospect helper and Retrospect Launcher were both set normally to Automatic and running normally. No errors were reported on these services at all, yet the auto-launch simply failed to happen each day. (I experimented by manually restarting these services but the issue remained.)

    Running Retrospect interactively resulted in the scheduled tasks running as soon as Retrospect was open.

    This is for my older version of Retrospect :

    I suspect that Security intelligence updates for Microsoft Defender Antivirus and other Microsoft antimalware KB2267602 Version 1.329.2549.0 was the cause. That's the only thing that happened to my system on the last day that my jobs fired successfully.


    However, following the installation of the optional update to Windows January 21, 2021—KB4598298 (OS Build 18363.1350) Preview ... which I installed yesterday ...  my scheduled Retrospect tasks are now firing up as normal again.


    Food for thought.

  2. Pardon me if I'm asking a silly question, but have you got the Retrospect Launcher Service set to "Automatic" under Windows Services?


    Even if you do ... perhaps try stopping it in the Services and restart it in the services then leave it set to automatic to see if that does anything to help.



  3. I wish I could point out where the issue is - but I'm just a fellow long-suffering customer of Retrospect ;)

    Maybe someone who is expert will jump in with some ideas...


    Happy to bung up some screen captures of what I am getting ... also just a quick look at the steps I'm doing in case you are doing something different (though I very much doubt that you are.)


    So, a look at the Retrospect screen where I select a session in reports and then File ... Export the backup set to a text file ... a look at the top of that text file ... and how it looks in Excel with a drag and drop ... attached.






  4. Hi x509,

    It is actually line by line ... but it is a very long line ...  you might need to change the resolution of the screen to see it all in Notepad.

    Alternatively ... If you open the .txt file in Excel and choose tab delineated during the import step, you could then clear out all the extra guff in the middle columns within Excel to make better sense of the filenames.




  5. 1 hour ago, mbennett said:


    According to Microsoft you can't uninstall One Drive in Windows 10, but you can turn it off, disable and hide it.  I'm assuming that you're not using W10, but other people might be confused by your advice.



    If that link doesn't work, Google the subject.


    In Windows 10 Home, I unlinked the account, turned off OneDrive and in Add / Remove programs, uninstalled it.

    That allowed me to then delete the OneDrive directories.

    True, the OneDrive folders returned later as visible in Windows Explorer ... but the issue with the directory is gone.

    Wonders never cease. 


    • Like 1
  6. That's very good info Scillonian.

    In my case, it turns out that no-one is actually using oneDrive as intended, so I have taken the "sledgehammer" approach ... "uninstalled" OneDrive and deleted all OneDrive directories.


    Problem solved. :lol:


    I can always re-install OneDrive later and implement a more elegant solution down the track. :)

  7. Interesting find ... well done to all. On my laptop, where 1803 was working fine with Retrospect, I was not logged in to Onedrive. The desktop which did have an account active with Onedrive, had the Retrospect jobs failing (except when run from within Retrospect using the Run drop-down.) I'm still puzzled why that was working ... Anyhow, I've unlinked the OneDrive account on the problem machine and will see if that does the trick.



  8. Hi again,

    Thought I would include a copy of the log from both a failed run (from the Retrospect Scheduler) and a successful run (from the "Run" menu drop down within Retrospect).


    From the failed scheduler run:

    +    Normal backup using Backup C at 5/05/2018 7:00 PM
            5/05/2018 7:00:15 PM: Finished scanning backup set data files
        To Backup Set Backup Set A...

    -    5/05/2018 7:00:14 PM: Copying Local Disk (C:)
        Scanning incomplete, error -1103 (write protected)        5/05/2018 7:01:03 PM: Compressing catalog file

    From the successful "Run menu drop-down" within Retrospect:

    +    Normal backup using Backup C at 6/05/2018 10:32 AM
            6/05/2018 10:32:24 AM: Finished scanning backup set data files
        To Backup Set Backup Set A...

    -    6/05/2018 10:32:23 AM: Copying Local Disk (C:)
            6/05/2018 10:33:22 AM: Found: 404,197 files, 88,163 folders, 82.0 GB
            6/05/2018 10:33:27 AM: Finished matching
            6/05/2018 10:33:34 AM: Copying: 9,042 files (7.8 GB) and 153 hard links
        6/05/2018 10:36:03 AM: Building Snapshot...
            6/05/2018 10:36:06 AM: Copying properties for 88,163 folders
            6/05/2018 10:36:18 AM: Finished copying properties for 88,163 folders and 0 files
            6/05/2018 10:36:18 AM: Copying UEFI System Partition
            6/05/2018 10:36:21 AM: Copying Snapshot: 418 files (406.8 MB)
            6/05/2018 10:36:30 AM: Snapshot stored, 406.8 MB
        6/05/2018 10:36:30 AM: Execution completed successfully        Completed: 9042 files, 7.9 GB
            Performance: 3333.7 MB/minute
            Duration: 00:04:06 (00:01:42 idle/loading/preparing)

            6/05/2018 10:36:30 AM: Compressing catalog file
            6/05/2018 10:36:31 AM: Compressing catalog file

  9. 1 hour ago, hevanw said:


    When you say interactively, do you mean using 'immediate backup' ? Also, is that a local backup or a backup of a remote machine ?

    I just tried 'immediate backup' on my server to backup my client device, and I'm again getting the -1103 error.

    No, what I'm doing is just entering Retrospect and selecting the Duplicate script job to run. For some reason it works for me when I do that, but the same job fails when fired off by the scheduler. This is a local "Duplicate C" job.


  10. Hi,

    I have the same error 1103 issue with Retrospect after updating to Windows 1803.


    Both Duplicate and backup jobs dealing with "C Drive" were failing. ("D Drive - a data drive -  was still working fine.)

    It does seem to be an issue with VSS permissions?


    Interestingly, when I ran the Duplication job "interactively" from within retrospect, the job was successful (although a duplication job that normally takes about 10 minutes took just over 2 hours.) This is because the job included the newly created Windows.old folder as well as the new Windows files that landed with the 1803 update.


    Something just over 230,000 files were involved.


    I then ran the Backup job "interactively" and that was also successful.

    Possibly some issue with a scheduled run not picking up that the user does have Admin rights?


    I have made no changes at all to VSS settings so I will be interested to see if the next scheduled Duplication and backup jobs fail again (non-interactive jobs).

    Food for thought?


  11. Hi,

    It is from a duplicate script on the server.


    Retrospect version 10.5

    I'm getting this same issue also on another Windows 10 PC running Retrospect version 12


    Same folder on both machines.

    Seems the Cortana update has created a weird folder that has some odd link between the folders:




    in the parent folder: 



    On further investigation, it had some odd user in the security settings, so I have removed that odd user id from the security properties and will see what happens on the next duplication run ...

    Thanks for your interest.


    I'll get back with any further updates ...

  12. Hi,

    Since the Feature Update to Windows the other week ...


    I'm getting this error:


    1/11/2017 10:20:36 AM: Creating folders
    1/11/2017 10:22:33 AM: Finished creating 55,697 folders
    1/11/2017 10:22:34 AM: Copying properties for 55,697 folders
    File "C:\Users\Phil\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\": can't read security information, error -1101 (file/directory not found)
    1/11/2017 10:27:09 AM: Finished copying properties for 55,697 folders and 0 files
    1/11/2017 10:27:12 AM: Copying properties for 55,697 folders
    Folder "C:\Users\Phil\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\": no security information, error -1 (unknown)
    1/11/2017 10:32:11 AM: Finished copying properties for 55,697 folders
    1/11/2017 10:32:15 AM: 28 execution errors
    Completed: 7687 files, 8.0 GB
    Performance: 382.9 MB/minute
    Duration: 00:31:45 (00:10:30 idle/loading/preparing)



    Anyone else?


    Is there a way to fix this?




  13. Just that although there would be a "duplicate file", the older file would be removed when the groom was run.


    In my opinion, I would rather have a backup of files that are currently on my machine, since renaming one in effect does create a "new" file. I think it would be confusing and somewhat difficult to implement the feature you are suggesting.


    Each to their own.

  14. Thanks, changing that to 100% fixed the problem.


    BTW, I also tried changing the allowed capacity to 500GB, but it snapped right back to 465GB. Any idea why Retrospect sets the allowed capacity to a figure significantly lower than the physical capacity of the drive?


    This is due to the manufacture's method of calculating what 500 GB means, vs how a computer sees that "500 GB" ...


    As explained here:



  • Create New...