Restore Point Creator — Beta Testing

A Public Beta version is being distributed. If you want to test it for me, you can download it using one of the links below. It's not ready for distribution but if you are having issues with the latest public version I suggest you download the Public Beta version and see if the fixes contained in it fix the issues you're having.

To instruct the program to download the release candidate versions, go to Program Options/Settings -> Software Update Settings -> Program Updates Channel -> Public Betas to receive new beta and release candidate updates. Then go to System Restore Point Utilities and click on the Check for Updates. The program will then tell you that you have a new version to download along with the changes to the public beta versions.

Please note that development is pretty fast in the beta channel and that new builds are released as soon as new code has been added. So if you don't like lots of updates and prefer updates to be a twice-a-month kind of thing, the beta channel isn't for you.


You can download the beta version using one of the URLs below depending upon which type of distribution package you want.

Version 6.7 Build 12 (Public Beta 3)

Public Beta 3 Changes
  • Forgot to increment the beta number.
Public Beta 2 Changes
  • Removed the seconds display from the bottom of the Application Event Log window because more often than not the seconds number was always 0.
  • Added additional wording the time display at the bottom of the Application Event Log window.
  • Converted logID variables from ULong to Long as per the specifications of the restorePointCreatorExportedLog() Class Object.
  • Made it so that corrupted log files are saved with an incremented number as part of the file name. This is to as to preserve older corrupted logs.
Public Beta 1 Changes
  • Removed a legacy settings variable.
  • Fixed a minor bug in which the log export function would be triggered even on a new installation.

  • Dl Cabling

    The ‘manage system restore storage space’ is greyed out…………

    • trparky

      Are you running Windows XP?

  • Dl Cabling

    Yes

  • Peter

    I found that RPC crashes on volumes that have *zero shadow storage* *allotted*. (The crash is in the command Manage System Restore Point Space and then clicking one of the volumes with zero shadow storage. My solution was to allot 1% from the System Control Panel on all volumes (short of remembering what volumes not to click).
    I found that RPC does not show the Manage button in View Disk Space Usage for volumes that have *zero shadow storage* *used*. This is not crashing, but strange.
    This is for version 2.6.3 and I reported on the Uninstall report page.
    Really and sincerely many thanks for RPC.

    • Peter

      Really and sincerely many thanks for RPC. (this means positively I installed version 2.6.3 again immediately after Uninstall and after having isolated the issue.)

      • trparky

        I have pushed out an update to correct the crash issue in the Manage System Restore Point Space tool. Build 10 is out now. The changelog reflects you as being the person who pointed the issue out to me.

  • Georges PapyNet

    Beta 8.2.6
    It’s OK for me

    But …. 3 times
    Running As: Système
    Message: (10,8):LogonType:
    Exception Type: System.Runtime.InteropServices.COMException

    The exception occurred à Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, TaskLogonType LogonType, Object sddl)
    à Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(String Path, TaskDefinition definition, TaskCreation createType, String UserId, String password, TaskLogonType LogonType, String sddl)
    à Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(String Path, TaskDefinition definition)
    à Restore_Point_Creator.My.MyApplication.addRunTimeTask(String taskName, String taskDescription, String taskEXEPath, String taskParameters)

    • Georges PapyNet

      it’s = with beta 3 (8.2.7)

      • Georges PapyNet

        Sorry
        it’s = with beta 5 (8.2.9

        • trparky

          What? Are you saying that the issue still exists in Beta 5? I don’t understand the “it’s = (insert version here)” part.

          • Georges PapyNet

            It’s OK avec la 2.8.10 (beta 6)
            W7 SP1 64 bits et W8.1 64 bits
            Georges

  • Vanya

    Hi there! Thanks for good prog! Is it possible to add such an option for “Protecting created Restore Point from automatic system deleting?”
    I have not found a something like “protection option from removing points” among Windows 7 itself, perhaps it can be done standard tools? Anyway I would like to see this option in your program! Thank you!
    I use Version 2.8 Build 4 stable
    Windows 7 Home Basic 64x

  • Georges PapyNet

    Version 2.8.11
    It’s OK for me
    W8.1 et W7 64 bits
    Bien cordialement
    Georges

    • Georges PapyNet

      Version 2.8.12

      It’s OK but a friend of W8.1 Dell IT: :

      “Message: La référence d’objet n’est pas définie à une instance d’un objet.
      Exception Type: System.NullReferenceException

      The exception occurred at Restore_Point_Creator.My.MyApplication.MyApplication_Startup(Object sender, StartupEventArgs e)
      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnStartup(StartupEventArgs eventArgs)
      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()”

      An idea, a track because no repair has solved the problem and we do not know what you are using Visual C ++

      Thanks

      • trparky

        Alright, download this file…
        http://www.toms-world.org/beta/RestorePointCreator.pdb

        That’s the debug symbol file for the program. Simply download it, put it into the same folder as the program, and then run the program again. When it crashes it should give far more information in terms of crash data.

        No, it’s not C++ that I write the program in, I use Visual Basic.NET (believe it or not).

        • Georges PapyNet

          Hello!
          Sorry
          I do not open .pdb
          Georges

          • trparky

            You don’t open a PDB file, you simply put it into the program’s folder and when the program crashes the .NET debugger and exception handlers now has the PDB file to get the debug symbols from.

          • Georges PapyNet

            Hello!
            OK I do this tomorrow
            my friend’s house

            OK je fais cela demain
            chez mon ami