Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Registry isolation doesn't work at all
Anonymous

Date:
Registry isolation doesn't work at all
Permalink   
 


Hi,
Registry isolation doesn't work at all.

Setup:
- I tried with latest 3.1.1446 and some other versions. Win10 64bit.
- your Irfanview package as an example:  IsolationMode=Isolated or DataMode,     Registy isolation= Isoloated or StrictlyIsollated on top hive and all other nodes

Test:   change a registry key through Irfanview
- start Irfanview, Menu\File\Open, then I navigate to C:\Windows
egedit.exe, rightklick\open
- regedit starts in context of Irfanview (and virtual layer?), checked with ProcessExplorer, regedit is a child process of Irfanview
- create a new key in HKEY_LOCAL_MACHINE\Software

Problem:  Key is created in host registry and not isolated. When I close Irfanview and open Regedit normally (Win+R,Regedit), the key is still there.

Am I missing something? According to isolation settings the registry should be untouched, except for the VOS hive...



__________________
Anonymous

Date:
Permalink   
 

Hi,

any info or statement on the above?
Is it fact that isolation doesn't work for child processes, if a packaged app launches an other exe ?
I'm praising your product as faster&simpler to a client who uses Thinapp, but if isolation doesn't work on child processes I don't have an argument any more.
Thanks.



__________________


Senior Member

Status: Offline
Posts: 268
Date:
Permalink   
 

Let me retry an answer here, different from the one I initially meant to write: isolation parameters are inherited.
However the virtualization context (execution within the "bubble") may not be happening in the exact scenario you are describing due to UAC *elevation*. In some cases Cameyo packages elevate child program executions as part of the bubble (yellow elevation dialog) and in other cases they just keep the child program elevated using the original (non-virtualized) context (blue elevation dialog, typically).
So this has to do with parent-to-child elevation virtualization / non-virtualization, not with isolation per-se.

__________________
Anonymous

Date:
Permalink   
 

Thanks for the info, good to know that in general the isolation should be inherited by child processes. I had doubts.

Is there any general rule, so it's predictable?


Kind of:
- if child process needs elevation it's not isolated any more?
- if child process is not part of the package and needs elevation it's not isolated any more?
etc.

 



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard