Bug: reg-import leads to truncated hex-data

15 views
Skip to first unread message

Matthias Gerhard

unread,
Oct 21, 2019, 10:30:00 AM10/21/19
to RegistryFinder
Hello,

thank you for this very useful tool. I discovered one bug, though:

File|Import|example.reg:

original data of example.reg:
[HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer]
"Windowplacement"=hex:2c,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,\
  00,ff,ff,ff,ff,ff,ff,ff,ff,fb,ff,ff,ff,02,00,00,00,92,06,00,00,f4,03,00,00

after import only truncated data can be found in Registry Finder:
[HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer]
"Windowplacement"=hex:2c,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00

Best regards, Sindbad

Salvia

unread,
Oct 23, 2019, 12:27:23 PM10/23/19
to RegistryFinder
I also tested this and I can confirm that this bug is present.
This is a VERY SERIOUS bug.

I tested the same feature with Windows Registry Editor.
The "import" function works fine there.

Please make a note of this bug and try fixing it as soon as possible sergei.


Sergey Filippov (Registry Finder)

unread,
Oct 26, 2019, 5:33:58 PM10/26/19
to RegistryFinder
Thank you guys for reporting that. I hope I will release a fix next week.

Salvia

unread,
Nov 4, 2019, 2:13:32 AM11/4/19
to RegistryFinder
I just uninstalled my version 2.34 and installed 2.39 to see if the issue is still there.

I can confirm that IT IS NOT THERE.

So, please consider this issue fixed, Sergey.
Reply all
Reply to author
Forward
0 new messages