Backup bug(s)

tullik

Certain backed up registry items do not restore with:

Backups-->Registry Backups-->Restore

Backups-->Registry Backups-->Custom restore

or even a Windows Registry Editor Version 5.00 import done outside of PT

See this quoted Entries.reg:

Windows Registry Editor Version 5.00

; File created by TBackupManager

; Component version: 1.5c

; Component used by: jv16 PowerTools X, MainForm: MainForm, ActiveForm: MainForm

; Program version: 4.0.0.1486

; File Description: Clean and fix my computer - Selected: 1, total: 47 (does not exist)

; Meta Description: Fix: True, Scan: 3, Optimize: False, Compact: False, Win: Windows 7 Home Premium, WinVer: 6.1.7601, Admin: True, FD: c, WinDir: C:\Windows\, SysDir: C:\Windows\system32\, AppDir: C:\Program Files\Macecraft\V\jv16 PowerTools X\4.0.0.1486\, App-b-Dir: C:\Program Files\Macecraft\V\jv16 PowerTools X\4.0.0.1486\Backups\, FV: True, SN: 8866-4384F23E-381246765, List.iCount: 47, List.cCount: 1, List.sCount: 0

; Application command line: "C:\Program Files\Macecraft\V\jv16 PowerTools X\4.0.0.1486\jv16PT.exe"

; Date: 06.05.2015

; Time: 22

"C:\PROGRAM FILES\BILLP STUDIOS\WINPATROL\WINPATROL.EXE"="03/30/2009 8 PM"

The problem is in the syntax put out by TBackupManager. The backslashes in the path text have to be doubled for regedit.exe to process the import correctly (regedit does not issue a message for the error; in effect, the path text is ignored by regedit).

This manually edited import restored the registry item:

Windows Registry Editor Version 5.00

"C:\\PROGRAM FILES\\BILLP STUDIOS\\WINPATROL\\WINPATROL.EXE"="03/30/2009 8 PM"

jv16

Nice catch! This bug is now fixed, thank you for reporting!

The bug only affects registry data where there is a filepath in the name of the entry, not in the value of the entry. These types of registry values are less common.

Also, the fix has been implemented in a way that the next time you use the program, it will automatically go through all your old registry backup files and checks if incorrect syntax lines exist in any of those backup files and automatically fixes them, as well. This happens when the program is next time used to create any backup file, for example, while cleaning the computer with CFMC.