Hi Jure,

- what's the return code from RegistryGet?
- can you see the value from Regedit?
- is the encrypted value a plain string (e.g. using n_cryptoapi Hex encoding) or not? You may need to try RegString!, RegExpandString!, RegBinary!, RegMultiString! depending on the encrypted sequence of bytes that you store.

Best,

.m

P.S.

PB now provides built-in object for encryption, you do not need Windows DLL and external functions any more:

https://docs.appeon.com/pb2019r2/objects_and_controls/ch02s15.html

Hi Marco ,

Thanks for the quick reply .

- what's the return code from RegistryGet?

1

- can you see the value from Regedit?

yes

- is the encrypted value a plain string (e.g. using n_cryptoapi Hex encoding) or not? You may need to try RegString!, RegExpandString!, RegBinary!, RegMultiString! depending on the encrypted sequence of bytes that you store.

yes plain string with RegString! parameter

what's the registry location?

Maybe you have a 32/64 bit location/permission issue (i.e. WOW6432Node hive)?

Best,

.m

Hi Marco ,

Quote:

I wanted to do the same thing by writing the encrypted data to the Registry (RegistrySet), but in some cases the RegistryGet function does NOT return the correct data.

1. After RegistryGet fails, do you find the value in the registry using "regedit.exe"?

2. Define "some cases": Is that for certain users, or on the same PC it can fail sometimes?

3. To which part of the registry are you writing. Lots of users have LOCAL_MACHINE protected for write.

Jure -

   Did you see Roland Smith's response?

Delete the two values and change your code to store it as RegBinary! with the encrypted string coming from a blob variable. Then you use RegBinary! with RegistryGet and convert to string.


Later -

Olan