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

Windows 10 CD/DVD-ROM issue

Hello all,

I believe I may have discovered an issue relating to Windows 10 and the Sophos endpoint agent.  I upgraded to Windows 10 yesterday and checked device manager to find that my DVD-RW was not functioning properly.  If I uninstall the device, rescan for hardware changes and let it automatically reinstall, it functions properly again.  Upon rebooting, the DVD-RW stops functioning again until I repeat the aforementioned steps.  I have noticed that after rebooting, a second driver is added for the DVD-RW from Sophos: sdcfilter.sys.  Presumably this is needed for the endpoint agent to perform device control functions such as blocking writable drivers which we do utilize in our environment.  I'm not positive this is causing the issue, but that evidence suggests that.  I am going to report this to Sophos support in hopes that it might be a bug that could be corrected in the upcoming 10.6 release for all those early adopters but I thought I'd post it on the forums as well in case anyone had a similar experience.  I've attached two screenshots to support my post.

J

:58206


This thread was automatically locked due to age.
  • The problems as been 'fixed' for me, in a way.  The CDROM breaks when my computers upgrade to 1803, but a reboot fixes it (until the next feature update, I assume).

  • On the next ide update (or any update requiring an actual update not just a check) post OS upgrade the SAV installer will recognise it is not a complete install and switch to a major install which will add the sdcfilter service back.  Microsoft does not migrate the driver as it's not PnP but it should be re-instated in a couple of hours depending on when the next ide update is released.

     

  • Unknown said:

    So my ticket got kicked back to the helpdesk, Global Escalations still claims the resolution for this issue is to manually reinstall scdfilter on every workstation after every Windows feature update. It is clear Sophos is not interested in resolving the issue properly.

    Can you DM me the reference case number so that I can have it checked with the team? If our users are still facing the issue post the fix, we would like to investigate it further to have it addressed.

    Regards,

    Gowtham Mani
    Community Support Engineer | Sophos Technical Support

    Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts
    If a post solves your question use the 'This helped me' link.