What does "Block removable media" mean exactly?

Discussion in 'ESET NOD32 Antivirus' started by loverboy, Nov 14, 2010.

Thread Status:
Not open for further replies.
  1. loverboy

    loverboy Registered Member

    Joined:
    Mar 25, 2009
    Posts:
    59
    In the Help file I read

    Does it mean that Autorun is disabled for USB pens?

    Does it mean that I cannot modify any file in a USB pen? (= I cannot write or delete files on it... does "block" mean that?)

    Does it mean that my USB drives (they are removable media) are "blocked" someway?
     
  2. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    those USB (and USB only) devices are not accessible by the OS, it does not impact the auto run settings of the OS, however due the inaccessibility autorun cannot be executed when this option is enabled. it does not apply to eSata or PCIe memory card readers such as SD/MMC/xD
     
  3. loverboy

    loverboy Registered Member

    Joined:
    Mar 25, 2009
    Posts:
    59
    Could you be more "easy"? :p

    When I talk about USB I mean
    - USB stick memories, or
    - USB "external" disk drives

    What is the practical behaviour with these two devices? ;)
     
  4. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    any USB device with a file system, be it stick, pen drive, navigation device, mobile phone, hard disk, the like. devices like USB TV or infrared receivers will still work properly.

    USB devices with a file system will be inaccessible by the OS, i.e. it cannot read the structure of the file system. with USB block enabled on 7x64 this pops up when inserting a USB stick

    14-11-2010 23-12-00.png

    in explorer it shows following when trying to access the USB media

    14-11-2010 23-14-23.png

    you may try it your end if the above does not suffice
     
  5. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Last edited: Nov 15, 2010
  6. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
  7. Zyrtec

    Zyrtec Registered Member

    Joined:
    Mar 4, 2008
    Posts:
    534
    Location:
    USA
  8. loverboy

    loverboy Registered Member

    Joined:
    Mar 25, 2009
    Posts:
    59
    Ok, guys, thanks you all.

    It seems to me that this feature, then, is useful as a last resource (or an emergency resource) and not to be used normally.
     
  9. BoerenkoolMetWorst

    BoerenkoolMetWorst Registered Member

    Joined:
    Dec 22, 2009
    Posts:
    3,771
    Location:
    Outer space
    Yes, though it can be handy on public or work pc's to prevent everyone from pluggin in their infected USB drives.
    But indeed, for personal use, it's more for like emergency :p
     
  10. tanstaafl

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    This is not true and my biggest complaint...

    Enabling this option also blocks IDE/EIDE (and I'm fairly sure SATA) based CD/DVD ROM drives, which makes it useless to me (since we need these).
     
  11. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    You can define exceptions for CD/DVDROM drives.
     
  12. tanstaafl

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    Some users have a D:, some an E:, and some are F: or G:... I can only define an exception for one that is on MY system when creating the policy, so no way to pre-define all of them...

    Regardless, I shouldn't have to. USB and IDE/SATA based devices should be considered separately - *and* it should be possible to provide read-only access (after scanning with advanced heuristics) to all, again, without having to add specific exceptions.
     
Thread Status:
Not open for further replies.