"Fully Virtualized" enabled by default?

[Syl]

hi there,
I updated and I read in the patch note that “Fully Virtualized” is a new option.
Is it enabled by default with a fresh install ? (I was in Partially Limited, but it doesn’t work most of the time).

I hope by virtualizing everything, programs should work now.

[Dch48]

The default should still be “Partially Limited”. The difference now is that you have the option of “Fully Virtualized” where before it took a registry hack to make that option visible.

[Syl]

ok thanks. I’ll try Fully Virtualized then. Partially Limited wasn’t working most of the time (apps crashing inside the sandbox), and I had to not isolate them, which defeat completely the purpose.

[Dch48]

Just be aware that when they are run virtualized, none of the things they do, including saving or remembering input will remain after they are closed. If the app is something you trust, want, and like, it should eventually be added to your trusted files list.

[Syl]

yep, but most of the time, Partially Limited wouldn’t work, even with a trusted app. I had to remove it from the sandbox to make it run.

I just hope it will work now, I don’t mind if it doesn’t keep anything (it’s much logical this way IMO, since it’s completely seperated).

[SanyaIV]

@Dch48 post:4

Just be aware that when they are run virtualized, none of the things they do, including saving or remembering input will remain after they are closed. If the app is something you trust, want, and like, it should eventually be added to your trusted files list.

I thought that I’d mention that the data isn’t lost when the application is closed. The data still remains in C:\VTRoot and is accessible by the application if it is run as virtualized again. However if you reset the sandbox the data will be lost, and if you run the program outside of the sandbox after having run it inside the sandbox then all data from inside the sandbox will now be inaccessible unless you move it to the correct direction or point the application to the place of this data.

So an application as fully virtualized will not lose any data from being closed, as long as it is started as fully virtualized again, if you want to start the program outside of the sandbox but still have the data from when it was inside the sandbox then you can navigate to C:\VTRoot (it’s hidden) and look for the data you want to save and then copy paste it into the correct direction of the real system.

[Dch48]

@SanyaIV post:6

I thought that I’d mention that the data isn’t lost when the application is closed. The data still remains in C:\VTRoot and is accessible by the application if it is run as virtualized again. However if you reset the sandbox the data will be lost, and if you run the program outside of the sandbox after having run it inside the sandbox then all data from inside the sandbox will now be inaccessible unless you move it to the correct direction or point the application to the place of this data.

So an application as fully virtualized will not lose any data from being closed, as long as it is started as fully virtualized again, if you want to start the program outside of the sandbox but still have the data from when it was inside the sandbox then you can navigate to C:\VTRoot (it’s hidden) and look for the data you want to save and then copy paste it into the correct direction of the real system.

That is a very good explanation. Unfortunately however, it seems that you have to reset the sandbox on a pretty regular basis to keep it functioning correctly. I have had to do it 3 or 4 times to make the Kiosk work right again.

[SanyaIV]

@Dch48 post:7

That is a very good explanation. Unfortunately however, it seems that you have to reset the sandbox on a pretty regular basis to keep it functioning correctly. I have had to do it 3 or 4 times to make the Kiosk work right again.

I don’t use the Kiosk so I wouldn’t know about that, however I’ve had Opera sandboxed for weeks without having to reset the sandbox (although I did reset it today, all those settings lost ^-^‘’)