Serious BUG in 32-bit Backup system (build 550)

redseujac

Look at the Code below: Backups (e.g. in Registry Cleaner) are created for the 32-bit version as if it were a 64-bit version. The "backed up" entries contain "WOW6432Node" which doesn't exist in the 32-bit registry.

Windows Registry Editor Version 5.00



; File created by TBackupTool
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2009
; Program version: 1.9.0.550
; File Description: Fout betreffende E:\XX\TEMP\VBE\MSForms.exdFout betreffende E:\XX\TEMP\VBE\RefEdit.exdFout betreffende E:\XX\TEMP\Word8.0\ShockwaveFlashObjects.exdFout betreffende Ongeldig ActiveX/DDE/COM/DCOM/OLE item
; Date: 01.04.2009
; Time: 17

.....


@="IBooleanExpression"
@="IBooleanExpression"


@="7"
@="7"


@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"
@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"

.....


@="IPrintersFolderFilter"
@="IPrintersFolderFilter"


@="6"
@="6"


@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"
@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"

.....


@="IBackgroundTask"
@="IBackgroundTask"


@="4"
@="4"


@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"
@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"

......


@="IEnumBooleanExpression"
@="IEnumBooleanExpression"


@="7"
@="7"


@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"
@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"

.....


@="IPMCWorkItem"
@="IPMCWorkItem"


@="4"
@="4"


@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"
@="{728BE448-D414-4ABF-8F53-81DE7BF90CEE}"

.....

So, when you want to restore the backups, it's useless because the 32-bit registry normally doesn't have that WOW6432Node, which exists exclusively in 64-bit, thus the backups can't be restored properly.

They create a WOW6432Node in HKEY_CURRENT_USER\Software and in HKEY_LOCAL_MACHINE\Software which obviously is wrong and useless.

What happened here?

Obviously 32-bit code got messed up (replaced) by 64-bit code when working on "fixes" for the 64-bit part of the program.

I'm not very amused with that. That shows lack of vigilance, attentiveness and concentration and/or lack of order and all that should be virtues of the programmer.

Please, dear developer, stop that mess and let the 32-bit version alone!

That 32-bit version worked rather well before you began messing around with that 64-bit version for a couple of 64-bit users.

I think the 95% 32-bit users have the right to work

safely

with their own version without a mix of 64-bit serious BUGs.

So, please, let the 32-bit version alone and if necessary create a

seperate

64-bit version. That way the 32-bit users won't get saddled with serious BUGS caused by the 64-bit work.

Warning

for the users: don't use the Registry Cleaner anymore until this serious BUG is fixed!!!

redseujac

FYI following backup of today (naturally with the same serious BUG):

Windows Registry Editor Version 5.00



; File created by TBackupTool
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2009
; Program version: 1.9.0.550
; File Description: Error relating to Obsolete software entryError relating to Useless file extensionInvalid file or directory reference
; Date: 18.04.2009
; Time: 13











"I:\\Downloads\\vbacodeprint_6.13.105.exe"=dword
"I:\\Downloads\\everestultimate501.exe"=dword



"HRZR_EHACNGU:\\Qbjaybnqf\\ionpbqrcevag6.13.rkr"=hex,00,00,00,06,00,00,00,F0,59,84,56,01,B9,C9,01

"HRZR_EHACVQY:\\Hfref\\Wnpdhrf\\Qrfxgbc\\Vpba Pbairegre Cyhf.yax"=hex,00,00,00,42,00,00,00,00,00,00,00,00,00,00,00

"HRZR_EHACNGU:\\Hfref\\Wnpdhrf\\Qrfxgbc\\um-fcp.rkr"=hex,00,00,00,06,00,00,00,20,00,EA,64,02,B9,C9,01

"HRZR_EHACNGU:\\Qbjaybnqf\\ionpbqrcevag_6.13.105.rkr"=hex,00,00,00,06,00,00,00,B0,73,DB,F7,01,B9,C9,01

"HRZR_EHACNGU:\\Qbphzragf\\Rkpry\\Fcernqfurrgf\\QnCebIrEO\\QnCebIrEO602XACarj.rkr"=hex,00,00,00,06,00,00,00,50,1F,4D,19,93,B7,C9,01

"HRZR_EHACNGU:\\Qbjaybnqf\\zby2010_frghc.rkr"=hex,00,00,00,06,00,00,00,70,3F,A9,AA,D7,AE,C9,01

"HRZR_EHACNGU:\\Cebtenz Svyrf\\Vpba Pbairegre Cyhf\\VpbaPbairegre.rkr"=hex,00,00,00,06,00,00,00,00,59,29,A2,6B,B8,C9,01

"HRZR_EHACNGU:\\Hfref\\Wnpdhrf\\Qrfxgbc\\xrltra.rkr"=hex,00,00,00,09,00,00,00,E0,64,34,D7,8D,BA,C9,01

"HRZR_EHACNGU:\\Qbphzragf\\Rkpry\\Fcernqfurrgf\\QnCebIrEO\\602XCp\\QnCebIrEO6_2X.rkr"=hex,00,00,00,07,00,00,00,20,82,03,8E,9C,BE,C9,01

"HRZR_EHACNGU:\\Qbphzragf\\Rkpry\\Fcernqfurrgf\\QnCebIrEO\\QnCebIrEO602XACp.rkr"=hex,00,00,00,0E,00,00,00,70,FA,B4,43,05,BD,C9,01

"HRZR_EHACNGU:\\Hfref\\Wnpdhrf\\Qrfxgbc\\HfreNffvfgIvrj.rkr"=hex,00,00,00,06,00,00,00,F0,2C,AF,ED,4C,BF,C9,01

"HRZR_EHACNGU:\\Hfref\\Wnpdhrf\\Qrfxgbc\\FuryyOntfIvrj.rkr"=hex,00,00,00,06,00,00,00,40,A0,95,3F,4C,BF,C9,01

"HRZR_EHACNGU:\\Hfref\\Wnpdhrf\\Qrfxgbc\\Bssvpr 2007 Xrlpunatre.rkr"=hex,00,00,00,06,00,00,00,00,4D,C7,2E,F1,B9,C9,01

"HRZR_EHACNGU:\\Qbjaybnqf\\rirerfghygvzngr501.rkr"=hex,00,00,00,06,00,00,00,30,C4,EF,ED,C1,B9,C9,01

"HRZR_EHACNGU:\\Qbjaybnqf\\frghc_cip-shyy.rkr"=hex,00,00,00,06,00,00,00,B0,41,29,81,1B,B9,C9,01

"HRZR_EHACNGU:\\Qbphzragf\\Rkpry\\Fcernqfurrgf\\QnCebIrEO\\QnCebIrEO60.rkr"=hex,00,00,00,06,00,00,00,40,AB,93,0A,EC,B9,C9,01

"HRZR_EHACNGU:\\Qbphzragf\\Rkpry\\Fcernqfurrgf\\QnCebIrEO\\QnCebIrEO602XACnf.rkr"=hex,00,00,00,07,00,00,00,40,66,C2,65,E8,B9,C9,01


"ResourceDir"="C:\\Program Files\\Common Files\\LightScribe\\res"


"C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Microsoft Diagnostics and Recovery Toolset\\"=""
"C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\LightScribe Direct Disc Labeling\\"="1"
"C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Debugging Tools for Windows (x86)\\"=""


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mdumpstk\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mformatting\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mformatting\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mremmon\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mattachproc\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mhealer\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mattachproc\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mattachproc\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Debugging Tools for Windows\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mdumpstk\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mformatting\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mremmon\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mhealer\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mhealer\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mdumpstk\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\Program Files\\Debugging Tools for Windows (x86)\\sdk\\samples\\mremmon\\"


"1692A0035B2B9884C99BC5A275D080DA"="C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Debugging Tools for Windows (x86)\\"

jv16

It seems to be a bug alright, you can easily fix the damaged backup files by using Notepad's (or other text editor's) find and replace feature (Ctrl+H in Notepad) to remove all the "WOW6432Node" references. So for example:

This bug will be fixed in the next released version, due out in next week.

jv16

I have now located and fixed the bug, a fixed version of the program will be released in a few minutes. Not only it fixes the cause that caused incorrect backups to be created, but it also automatically fixes any found such damaged backup file when user attempts to restore it.

So nothing very serious, I'm glad to say. But this issue did show some improvement in the program's internal Safey Net feature that has been designed to automatically detect issues like this before they can cause any problems.

jv16

Fixed version is now released, thank you for reporting!

redseujac

jv16 wrote
...So nothing very serious, I'm glad to say. But this issue did show some improvement in the program's internal Safey Net feature that has been designed to automatically detect issues like this before they can cause any problems.

Well, I don't understand the statement about the Safety Net feature that automatically detect issues like this!

The users have detected and reported the problem, NOT that feature I guess?

redseujac

jv16 wrote
... you can easily fix the damaged backup files by using Notepad's (or other text editor's) find and replace feature (Ctrl+H in Notepad) to remove all the "WOW6432Node" references...

OK, I had figured out that already, but that's no point: what about the novice users who didn't figured out that?

But thanks for the quick update which was the only right solution for the problem.

jv16

redseujac wrote
jv16 wrote...So nothing very serious, I'm glad to say. But this issue did show some improvement in the program's internal Safey Net feature that has been designed to automatically detect issues like this before they can cause any problems.

Well, I don't understand the statement about the Safety Net feature that automatically detect issues like this!

The users have detected and reported the problem, NOT that feature I guess?

Yes, I ment that there is room for improvement in the Safety Net so in the future it would detect this type of issues as well.

redseujac

OK, I understand now, you meant some improvement is necessary in the feature, but "is necessary" dropped from your sentence :

redseujac

jv16 wrote
Fixed version is now released, thank you for reporting!

Checked it: fixed indeed !

And ... when restoring the "wrong" backups, the wrong part is also automatically fixed, i.e. ""WOW6432Node" is dropped.