Application Virtualization TechCenter >
Microsoft Application Virtualization (App-V) Forums
>
App-V General Sequencing
>
ShellNoRoam Registry Key
ShellNoRoam Registry Key
- Hi
We have a couple of sequenced applications that every now and again freeze up. On inspection the application is continually looping through HKCU\Software\Microsoft\Windows\ShellNoRoam\in the regsitry.
To work around this I added the following line to the OSD file:
<SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="FALSE" WAIT="TRUE" TIMEOUT="0">
<SCRIPTBODY>REG DELETE HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam /f</SCRIPTBODY>
</SCRIPT>
This appeared to fix thye problem when we were testing but it's back with avengence now. The only way to get back to the application is to kill the process.
Has anybody come across this problem before?
Regards
All Replies
- Hi,
Cannot say that I have come across this problem, but have you checked if your sequence contains that key in virtual registry? And if so, what if you delete it away? I usually remove those type of keys from every sequence I make as they do not relate to actual application but rather have Windows' own stuff in it.
/Kalle - The best solution will be to add the reg key in the exclusion list so you dont have to clean it everytime.
thanks
mayank
GNU Developer by choice .... - If I look at the Sequence using the SFT explorer that key doesn't exist. If I exclude the key in the package will it stop it been created when the package is running even though it doesn't exist in the sequence?
- If your application is creating the keys then they will be generated when you start your application. Also try to set the TERMINATECHILDREN="True" in the OSD file and see if that helps.
GNU Developer by choice .... - mad_oatcake said:
<SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="FALSE" WAIT="TRUE" TIMEOUT="0">
<SCRIPTBODY>REG DELETE HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam /f</SCRIPTBODY>
</SCRIPT>
This appeared to fix thye problem when we were testing but it's back with avengence now. The only way to get back to the application is to kill the process.
Btw, your problem with that script might be due to fact that PROTECT="FALSE" instead of PROTECT="TRUE", sorry for not spotting that earlier on. If that key gets cached inside the VE, deleting key from physical registry won't do any good as virtual copy will overlay it..
br,
Kalle