Maybe a bug ?
I've found that the EnumRegKey directive won't accept $R1-$R9 registers for the index parameter.
Maybe EnumRegValue will have the same issue...
Anyone found something about this issue?
Archive: Maybe a bug ?
Maybe a bug ?
I've found that the EnumRegKey directive won't accept $R1-$R9 registers for the index parameter.
Maybe EnumRegValue will have the same issue...
Anyone found something about this issue?
Sorry, I've made a terrible mistake in the script...
Anyway,
looping the statemant for walking the registry structure, the order of the keys found by EnumRegKey is fuzzy...
In my RegEdit I find them in alphabetical order (1-2-3), but looping EnumRegKey I find them in a strange order (3-1-2)...
Again, sorry for my silly bug submit!!
NSIS uses the Windows API call RegEnumKey. The Microsoft documentation for this call states "Because subkeys are not ordered, any new subkey will have an arbitrary index. This means that the function may return subkeys in any order". This is probably why you are not seeing them in the order you expect. I suspect RegEdit is forcing an order on them when it shows you them.