Author: myurkus
Subject: Load Column sets "test" still - v15.4
Posted: 06 January 2014 at 9:07pm
I was spinning on this for a while; including clearing out the registry keys procexp creates on first-launch. However, I am seeing the same issue. Has any fix/work-around been discovered?
FYI this registry key and its sub-keys are created upon the first time a user runs procexp.exe :
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer
As one adds/modifies/removes column sets, one can see the corresponding key-updates:
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet0
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet1
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet2
etc...
(Sometimes you have to close Process Explorer and re-open before a change in one of the values is persisted in the registry. However, it seems to correctly handle adds/modifies/deletes etc.)
The real issue is the only Column Set displayed as an option under "Load Column Set" is "test".
This is the case even when the "test" entry is deleted or re-named using the other CRUD methods. (This indicates hard-coding.)
I am a software engineer; I think I understand the issue. Either during new development, or more likely when fixing a bug, some developer had a place-holder when querying the available column sets that was hard-coded to return one item called "test." It was probably temporarily put in place to isolate some other issue; however, the developer then checked in the code without swapping it back to the "real" method to return the actual list of available Column sets.
Unless there is some other way of loading a column set (the stop-gap may even be in the view/presentation layer, so if this can be set elsewhere in the application, it should work.) I cannot think of any workaround without access to the source-code..
I hope this helps; please let me know if I can be of any assistance. At this point I have delved enough into the problem that I can probably fix it myself if I had access to the source code. So if someone wants I would be happy to fix it...
Thanks for your time reading this; I hope this helps. And again, please let me know if I can be of further help.
MikeY
Michael Yurkus
Subject: Load Column sets "test" still - v15.4
Posted: 06 January 2014 at 9:07pm
I was spinning on this for a while; including clearing out the registry keys procexp creates on first-launch. However, I am seeing the same issue. Has any fix/work-around been discovered?
FYI this registry key and its sub-keys are created upon the first time a user runs procexp.exe :
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer
As one adds/modifies/removes column sets, one can see the corresponding key-updates:
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet0
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet1
HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer\ColumnSet2
etc...
(Sometimes you have to close Process Explorer and re-open before a change in one of the values is persisted in the registry. However, it seems to correctly handle adds/modifies/deletes etc.)
The real issue is the only Column Set displayed as an option under "Load Column Set" is "test".
This is the case even when the "test" entry is deleted or re-named using the other CRUD methods. (This indicates hard-coding.)
I am a software engineer; I think I understand the issue. Either during new development, or more likely when fixing a bug, some developer had a place-holder when querying the available column sets that was hard-coded to return one item called "test." It was probably temporarily put in place to isolate some other issue; however, the developer then checked in the code without swapping it back to the "real" method to return the actual list of available Column sets.
Unless there is some other way of loading a column set (the stop-gap may even be in the view/presentation layer, so if this can be set elsewhere in the application, it should work.) I cannot think of any workaround without access to the source-code..
I hope this helps; please let me know if I can be of any assistance. At this point I have delved enough into the problem that I can probably fix it myself if I had access to the source code. So if someone wants I would be happy to fix it...
Thanks for your time reading this; I hope this helps. And again, please let me know if I can be of further help.
MikeY
Michael Yurkus