Issue with cscript/wscript breaking outside the AppV 5 bubble when run inside the bubble.

Question

I'm working on sequencing an application (EPIC) and they have a debugging script that runs that executes their application and their debugging application immediately afterwards with some parameters.  When I try running this script inside the AppV 5
bubble from a command prompt it fails.  I've found the issue appears to be that cscript and wscript are looking for the registry values it requires
outside the bubble.  I've shortened their script and the registry key required to minimize the noise of this problem.  The VBS script is:
'========================================================
Dim sEpicInstall, oCtx, oFSO, oReg, oLocator, oServices, oInstallDrive
Const HKEY_LOCAL_MACHINE = &H80000002
Set oCtx = CreateObject("WbemScripting.SWbemNamedValueSet")
Call oCtx.Add("__ProviderArchitecture", 32)
Call oCtx.Add("__RequiredArchitecture", TRUE)
Set oLocator = CreateObject("Wbemscripting.SWbemLocator")
Set oServices = oLocator.ConnectServer(".","root\default", , , , , , oCtx)
Set oReg = oServices.Get("StdRegProv")
Call oReg.GetStringValue(HKEY_LOCAL_MACHINE, "SOFTWARE\Epic Systems Corporation\Install", "79", sEpicInstall)
Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oInstallDrive = oFSO.GetDrive(oFSO.GetDriveName(sEpicInstall))
'===========================================================
The registry key that exists inside the bubble looks like so:
===========================================================
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Epic Systems Corporation\Install]
"79"="C:\\Program Files (x86)\\Epic\\v7.9"
===========================================================
if run inside the bubble this is the result I get:
If I add the registry key to the system itself and execute the command outside the bubble it works without issue:
So...  I'm assuming this is a bug in AppV 5?  Is there a reason why cscript/wscript can break outside the environment or is there a reason why this script is able to do so?

Answer 1

You should probably start a new thread for this as it's a new question, and a different problem than the original post.
I have not tried the above, but have you made sure IE is closed before running it? If IE is already running outside of the bubble when you run the script, it could use the existing IE process rather than create a new one inside the bubble.
As far as I know, .vbs files should run inside the bubble unlike cmd/bat files when targeted directly by the shortcut. But it is worth trying modifying the shortcut to point to wscript.exe with the script supplied as a parameter, just to rule it out.
Another option to look into is to target your shortcut to iexplore.exe directly, and apply the changes to hide the toolbar and status bar either via additional command line parameters, or via registry configuration if this is possible.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn