Jump to content

SmokeAndMirrors

Members
  • Content count

    6
  • Joined

  • Last visited

  • Days Won

    2

SmokeAndMirrors last won the day on November 20 2012

SmokeAndMirrors had the most liked content!

Community Reputation

2 Neutral

About SmokeAndMirrors

  • Rank
    Occasional forum poster
  1. Can somebody help me resolve my recent problem with Retrospect not backing up the system state? Read on for more details about this problem. Just recently, Retrospect 12.x for Windows on my laptop PC will no longer backup the System State. Instead, I get the following error messages in the Retrospect logfile: 12/30/2017 02:48:51: Copying UEFI System Partition [*] doCopyESPToDirectory: could not export BCD to State folder, sys_err=1, osErrNo=0 [*] WinXPMetaLoc::XPMdStoreESP: CopyESPToDirectory failed, err = -1,001 Can't back up System State, error -1001 (unknown Windows OS error) I am currently running "Retrospect 12.6.1.101 for Windows" [Release date November 13, 2017] on my HP Envy 17" laptop. The only thing that I did recently on that laptop was to upgrade its BIOS using HP's latest BIOS upgrade pack for that particular laptop. Prior to this BIOS update, Retrospect was able to backup the System State successfully. Then, about a month passed during which several things changed/updated on my laptop, but the only one that I can think might have a bearing on this problem is that BIOS update. Prior to that recent BIOS update, I was running this version of the BIOS as reported by Windows System Information: BIOS Version/Date Insyde F.35, 03/03/2016 SMBIOS Version 2.8 Embedded Controller Version 64.36 BIOS Mode UEFI After that BIOS update, I am now running this latest BIOS version as reported by Windows System Information: BIOS Version/Date: Insyde F.46, 10/27/2017 SMBIOS Version: 2.8 Embedded Controller Version 64.40 BIOS Mode: UEFI I've tried various ways around the problem of Retrospect not being able to backup the system state but nothing has worked so far. I've run Retrospect "AS ADMINISTRATOR" and still get the same error messages. I've made sure Retrospect is upgraded to the latest available version. Any help would be appreciated. Regards, Tony
  2. I've been using Retrospect 11.x for awhile now without any problems on my Windows 10 laptop. Just today (2/2/17), it backups fine but then when the verification step starts it cannot locate the backup set. Anybody else experiencing this? The external disk drive containing the backup set is good. I can locate the backup manually in File Explorer just fine.
  3. Hi, I created a Retrospect 11.x "Emergency Recovery Disc" (ERD) on my HP laptop running Windows 10 Professional. The ERD boots but when I select the "Restore locally" option the Retrospect.exe (application) never starts. Any ideas on how to fix this? Regards, Tony
  4. Retrospect 11 - Cannot Create Recovery Disc

    I recently upgraded to Retrospect 11 from 10. For disaster recovery purposes, I tried to create a bootable flash drive using Retrospect's "Disaster Recovery" option. Unfortunately, when I select "Create a bootable flash drive" (using an brand new SanDisk Extreme 64 GB), Retrospect runs and says it's putting several (14+) files to somewhere, but the flash drive is EMPTY! even though Retrospect says it has successfully completed the operation. Any ideas on how to resolve this?
  5. Retrospect 11 - Cannot Create Recovery Disc

    I recently upgraded to Retrospect 11 for Windows Desktop. After upgrading, I got the same error as you when trying to create an Emergency Repair disc (to DVD). The workaround that worked for me was to run Retrospect as Administrator (even though when I got the error I was logged onto an account with admin. privileges...go figure).
  6. I had the same problem as "sbgraphic". I'd follow Retropect's article on how to disable the RetroISA process but everytime something would reset the the "0" back to "1" in the RetroISA.ini file. I think Retrospect support forgot to include the "-w" option/switch in their article. Here's the command with the -w option/switch: sudo launchctl unload -w /Library/LaunchDaemons/com.retrospect.retroisa.plist Note: The key is ithe "-w" option/switch in the launchctl command. Here's how I finally got the Retrospect RetroISA process (daemon) to stop running on my iMac: Changed the permissions on the RetroISA.ini file to allow "admin" read & write. Modified that RetroISA.ini file: Changed StartRetroISA=1 to StartRetroISA=0 [Note: Disabled all volume scanning] Started Terminal.app to enter these UNIX commands as follows: sudo launchctl unload -w /Library/LaunchDaemons/com.retrospect.retroisa.plist [Note: According to my Google search, the "-w" option permanently keeps daemon from running (so RetroISA should no longer start-up again on re-boots of iMac)] [Note: The -w option used to actually change the *.plist file but now (under MAC OS X 10.?) it does NOT change the DISABLED key in the plist file but rather stores the DISABLED=TRUE status elsewhere on disk]
×