virtual root (FAT 32 not supported issue)

I installed CIS 4.0.X.779 in two hard disks
In one hard disk it didn’t create virtual root folder the OS is Win XP32 with FAT32 partition
It had a Security software avast 5.x on it.
In second hard disk it created virtual root folder the OS is Win XP32 with NTFS partition with no other security software.

Both hard disks not used simultaneously.Both OS are installed not in C:\drive.Sandbox enabled,filesystem virtualisation checked, registry virtualisation checked. show hidden files and folder enabled.

In second hard disk no files created in Virtual root folder when firefox run as untrusted with sandbox enabled.
also it saved the page on the desktop.

Is sandbox works only with NTFS file system and sytem files in c:\drive

Interesting. BTW if the directory is called C:\VritualRoot (all one word, note mis-spelling of virtual). Just in case you searched for it :slight_smile:

Anyone out there with a FAT32 partition? Do you get a C:\vritualroot directory?

If there is no answer could you try re-installing please with Avast disabled, preferably uninstalled. Could you also please check that the computer with a FAT32 partition has a 32bit processor (the sandbox does not work under XP64). Probably goes without saying …but…

Also please try running other applications virtualised in the sandbox. Note that automatic sandboxing does not virtualise.

Both OS are installed not in C:\drive.

Can you please confirm you mean that in both cases the OS is installed on a drive other than C:

Anyone else out there with the OS on a different drive? Do you get a C:\vritualroot directory?

Best wishes

Mouse
Best wishes

Mouse

Hi, i’ve installed XP on other drive letter, got no problems with it. Anyway, there’s no good reason to use FAT32… (slower, not secure and less capacity). Can you please confirm your set parameters:
Start → Run… →

cmd /k set

Check HomeDrive & SystemDrive infos, please.

Add one more case of VirtaulRoot (one word, with Virtaul correct spell) in a PC running Windows XP SP3 (and about 80+ Microsoft fixes), with drive NTFS formatted.
Used to run Comodo Firewall (only) and Avast 5! Free edition.
Removed avast!, and activated Comodo antivirus (current version: 4.0.138377.779, virus databse: 4560).
VirtualRoot folder has size zero, does not contain any other file or folder inside it, and is located at C: the same drive where operating system is running.
Initially suspected it belonged to Sandbox, that I am not using (not the kind of user who installs applications every other day)
Just deleted it, with apparent no side effects. Letting time do its job, and show if: 1) no side effets are permanent; 2) VirtualRoot folder will not raise from the dead.

Jose Pinho

Just to check - the spelling of the folder you have is “VirtaulRoot” NOT the normal “VritualRoot”? If so that is really wierd!

You could try restoring the directory from the recycle bin, then running a program deliberately in the sandbox using ‘add a program to the sandbox’. A browser is a good choice. Then browse around a bit. You should then get some data in you program directory.

Remember only files updated after program installation eg data and settings files are virtualised. Please see the Introduction to the Sandbox for more information.

Best wishes

Mouse

Hi Mouse,

You are correct. The folder name is Vritual, and it is back, at C: .
And now, I presume to have a cause and effect relationship, for what I am seeing here.
Yesterady night here in Brazil, I installed a program that can be called, in English, Income Taxes Annual Adjustment (equivalent to US government IRS´s Income Tax Statement). Since the program tries to run with a high level of privileges, Sandbox immediately. puts it into Sandbox. If I chek the option not to run the application in the sandbox, life goes on (I can run the software outside Sandbox). But, at this time, VritualRoot is already created (I presume, since I just noticed its presence this morning when checking for it).
So based on what I´ve seen here and found elsewhere in Comodo´s forum, VritualRoot (hard to type it this way …), is created whenever a program is appointed to run in the Sanbox.
Case closed, to me.

Sounds about right apart from the ‘high level of privileges’. CIS sandboxes all software unknown to it, except software that it thinks is an installer. It recognises installers in part by the fact that they ask to run under a user account with administrator privileges.

You’ll find it all explained in the Intro to the sandbox, link in my signature. Note that the CIS sandbox does not work like most sandboxes!

Best wishes

Mouse

contd…
It is Still getting strange.
Regarding to first instance of fat32 once a while the virtual root(sorry my mistake it is “Vritual”) appeared. It is in same drive that system files resides. Now again the is disappeared from the drive.
I have some more doubts raised.
Is virtualisation should be enabled in BIOS for the sandbox to work.(ihave disabled the option in bios)
Is sandbox works only for Physical partition not for logical partitions. ???

  1. I doubt that a bios setting can affect CIS, as the CIS sandbox work with OS facilities. But I don’t know for sure.

Anyone else know?

  1. Disappearing VritualRoot - strange I agree. Try manually sandboxing an app, maybe a secondary browser, with virtualisation on. Use the browser for a while, and leave it sandboxed. If VritualRoot disappears while it is still sandboxed there is certainly a problem. Otherwise I suppose it could be due to some form of housekeeping by CIS. But why it would appear again, unless you are sandboxing files, I don’t know. Possibly it appears when files are autosandboxed - even though they are not currently virtualised, they probably will be in future. It may disappear for housekeeping reasons if all autosandboxed files are declared safe?

  2. I’m afraid I cannot help re physical and logical partitions.

Anyone else know?

Best wishes

Mouse