Skip to main content

tdrpman174 and snapman380 drivers

Thread needs solution

Hi, are these two drivers actually needed or used when I don't have a Secure Zone or use Try & Decide?

The only thing TI 12 is used for is making backups so my question would be if disabling those two drivers, better setting their startup type away from 'boot', would affect making backups or mount images?

You can give me an honest answer, I am not the average user and the way TI makes backups on my system is strictly on-demand only. All autostart items and services installed by True Image have been disabled or set to manual.

0 Users found this helpful

Hello gunna!

Welcome to our Forum, it's nice to have you with us!

Snapman is required for creation of snapshot without which no backup creation is possible, and tdrpman is mostly responsible for Try and Decide mode, but we strongly do not recommend to touch it (disable, remove, modify) since it will cause issues with integration of Acronis True Image Home into the system, and may lead to unpredictable consequences (even BSOD).

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you.

Hello and thanks for replying. I was pretty much aiming at reducing the risk of BSODs by minimizing running 3rd party low level file system services/drivers. Since there is no sign of having the Scheduler2 service running only when needed is producing any conflicts I was wondering if the two drivers have to be loaded with the OS or could be started in the same matter. If you take the Udfs driver for example, it is only started when needed.

I guess my real question should have been: Do those drivers act as a layer of communication between OS and disk all the time once they are installed - or get active only when called by an Acronis feature. In which case they 'should' be safely set to something other than boot startup. My assumption might be wrong..

As far as I know, drivers installed and used that way get used all the time. This is what causes problems like media card readers not showing up and things like that if they don't work correctly. It can also cause problems if multiple imaging programs are installed (those that install their own drivers) since information/data must pass through each previous driver in the list.