This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Device Control Unable to block the USB

The Device Control Unable to block the USB.

Verified the as below:

1. Device control service working fine

2. The device control log able to read

3. The Endpoint conected and comply with group policy accordingly to block USB.

Enconter issue noe as below from the console under the issued Endpoint :

Device control failed when checking volume access: device control=\Device\cdRom0, error Code=0x8000ffff, (0xa052000d).


In other hand, other Endpoint according the policy and block the USB. Kindly advise :smileysad:

:39633


This thread was automatically locked due to age.
  • Hello Lingesvran,

    block USB

    Device Control is - as the Overview of Sophos device control in Endpoint Security and Control says - "port agnostic". Consequently you don't (and can't) block USB but certain device types. The message talks about cdRom0 so the settings for Optical drive should apply here.

    So - is this an external CD/DVD drive and if, are you saying that the same device is successfully blocked on other machines (do you have the associated message)? Haven't encountered this message so I can't say what checking volume access means, the error code seems to be a general one. Also I've found no corresponding article so I'd suggest you contact Support.

    Christian

    :39717
  • FYI that, the laptop fujitsu and we figure out the problem to block the USB device type such as KINGMAX and we tried KINGSTON also never block the the USB device. The error was shown device control service failed to stop (0x80004005). When check the console the  workstation on group and also applied with group policy. At the workstation SAV Endpoint showing the logs of which stated above and volume access error. On the regedit there's no log/empty stored for device control but other service have log.

    Kindly advise us. Seeking your coopearation.

    :39959
  • Hello Lingesvran,

    as said it'd be necessary to contact Support directly. Might be a good idea to collect the logs before doing so.

    Christian

    :39963