hollidayjr

I don't have any PST files but apparently you do!

Yes, FIXED. Thanks to you and Alex for the timely response.

2.2.0.891 does not work-it has the same problems as 2.2.0.900.

With .890 everything runs fine.

Yes, it prevents defender from updating, have to shut down drivepool. I will try .890 and let you know.

File sent, thanks. I rebooted several times to hopefully capture whats happening. Defender still fails on every other boot. One of my computers is a clean install with nothing but drivepool on it. Very strange.

I am using Win 10(1709) with Win Defender all updated with the latest updates. I also run Drivepool 2.2.0.900RC. This past week Defender was updated with a new antimalware client to version 4.12.17007.18011. I understand from reading that Microsoft made some changes under the hood to defender. Now every other time I boot the computer defender fails to start completely. I reboot the computer and defender works normally. I reboot the computer and defender fails completely. It will do this repeatedly and I have the same setup on two computers and both behave the same. How can it fail on one boot but not the next? Very strange. Anyway, I went back to a previous version of drivepool (2.2.0.881beta) and all is normal on both computers. I tried some of the more recent betas such as .896 and they have the same problem with defender. Please help as I would like to update to the latest version when it is released. I also noticed that the remote control feature doesn't work on the latest betas/RC but it does on the older versions such as .881beta. Thanks, Walt