My problem is it is not just me. I have several hundred people in multiple states and countries using the code. Randomly we have a machine that hangs and then the user install will fail.
I was hoping that this problem may have been seen and understood some time in the past.
What we don't understand is why the "setx" command will always work when the Broadcast() fails. There must be something Microsoft does with "setx" that is different then the module. My hope would be that this could be figured out and fixed so others don't have problems.
We have found some talk about Google Desktop and a service called NMIndexingService (part Nero software) being culprits in this hang.
In reply to Re^4: how do you propagate Tie::Registry modifications to the system environment (UtS,L)
by warrendodge
in thread how do you propagate Tie::Registry modifications to the system environment
by warrendodge
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |