CIS Premium 10 on Win 8.1.
Auto-Containment is enabled.
A folder with multiple install exe’s is added to containment configuration, set to run virtually, see screenshot.
Containment settings - see screenshot. ‘Do not virtualize’ - only folders are ‘shared folder’.
I can install a contained program, but once installed, cannot find a way to run it again. It’s exe in the VTRoot folder is unclickable from within explorer, and does not respond to being clicked from ‘run virtual’ from within CIS.
Where and how do I start a permanently contained program?
Try changing the block auto-containment rule for target containment folders to run virtually.
I believe I already have that set up that way - see attachment. Let me know otherwise.
PS: Installing an application in the container is not a problem - it’s starting it thereafter - from where, how can it be run?
I miss understood what you were trying to do. Use the run virtual task and select create a virtual desktop shortcut option and choose explorer.exe from the windows directory. Or you can use virtual desktop and have a link to my computer on the desktop.
I’ve already done this.
I install an application via the ‘run virtual’ button in CIS, select 'create shortcut on desktop, and finish the install. Then there’s a shortcut on the desktop, but clicking it only leads to installing the program again, not running it. It leads back to the installer. When Instead I hunt down the application executable, in the VTRroot folder somewhere, sometimes I can launch it from there, other times not.
Virtual Desktop I happen to not have installed as I don’t run silverlight or comodo browser.
You’re using the run virtual to run the setup application and not the actual installed executable. Use run virtual and browse to explorer.exe and select create desktop shortcut. Then open the virtual explorer desktop shortcut to open Windows explorer in containment which will show the contents of the container. Then browse to where you installed the application using the virtual instance of Windows explorer. e.g. C:\Program Files\installed app and not the vtroot folder.
I’m beginning to see
1, use ‘run virtual’ to install a program
2, use ‘run virtual’ again to locate windows explorer and create shortcut to desktop
3, use that shortcut to find the installed program in eg program files
4, find the executable, and run it from there.
5, that virtualized explorer shortcut can really stay, and be used again and again to find and fire up contained apps.
Yes and for virtual desktop you don’t have to install silverlight or dragon for it to work, and VD is not an extra component that needs to be installed as it already comes with CAV/CFW/CIS.
Well this is aweseome! I’ve never seen all that written up anywhere, and I’ve looked hard for a long time
It seems when opening the contained application from within vtroot I still have better luck. Some apps crash when opened via the virtualized explorer, but are ok when fired up from within vtroot, such as ACDsee 20. Fires fine from within vtroot, but crashes upon starting when fired from within the virtualized explorer.
So using a virtual desktop would amount to the same effect then than the ‘run virtual’ button/process? If so, does one have an advantage of the other?
Btw, not my experience that VD is ready ot go - see screenshot. I’m having the same prompt on a fresh win 10 platform.
If you click no it will still open, if you have silverlight installed you can use tablet mode inside the VD instead of just classic mode. So again not necessary to have either/or both extra items installed to use VD.
Some apps need full access to work which they don’t get when fun in containment so yeah its normal.
So using a virtual desktop would amount to the same effect then than the 'run virtual' button/process? If so, does one have an advantage of the other?
Yes its just a matter of convenience and preference you can use either way to run applications installed in containment.
You’re awesome - I finally understand how it works in Comodo. Thanks a trillion!
Re: some apps crashing when started via virtualized explorer but NOT crashing when run from within vtroot - both are still virtualized, are they? Or is the app virtually installed in vtroot but NO LONGER virtualized when actually run it from within vtroot?
When run from vtroot they don’t run fully virtualized but when you use virtualized explorer then they are run in containment/fully virtualized. If it has a green border around the applications window then it is being run fully virtualized.
Thank you. You’ve saved me countless hours. I bet many people would be delighted if you posted summarized instructions somewhere