Strange Problem with Defender

[hollidayjr 0]

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

[Christopher (Drashna) 632]

The main change that happened here is how the pool is mounted, and the timing around it.  Nothing that should cause this sort of issue.

But if you could, install the RC again, and enable boot logging:
http://wiki.covecube.com/StableBit_DrivePool_2.x_Boot_Time_Log_Collection

[hollidayjr 0]

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.

[Christopher (Drashna) 632]

Could you see if this happens wit 2.2.0.890? 
http://dl.covecube.com/DrivePoolWindows/beta/download/?C=N;O=D

If not, then it's the new mounting code that is causing the issue. 

 

Also, I was going to test this... I can't get the update for this version to even INSTALL.... 

[hollidayjr 0]

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

[hollidayjr 0]

With .890 everything runs fine.

[Christopher (Drashna) 632]

/sigh

Then yeah, it's the new mounting code that is the cause of this issue. 

And unfortunately, on the systems that I can get the update working on, don't show this issue. 

I've flagged the issue and logs for Alex 

https://stablebit.com/Admin/IssueAnalysis/27727

 

Also, could you try 2.2.0.891, and see if this happens? 

[hollidayjr 0]

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

[Christopher (Drashna) 632]

Yup, that's the first build with the pool mounting changes in it. 

So that's definitely the cause...

[Christopher (Drashna) 632]

Alex believes he has identified the issue, and should have a fix for it out soon.

That said, it's not the mounting code change that cause this, specifically, but made it more likely to occur.

It's a very, very weird bug. Emphasis on "weird".

[Christopher (Drashna) 632]

This should be fixed in 2.2.0.902:
http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.0.902_x64_RC.exe

[hollidayjr 0]

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

[Christopher (Drashna) 632]

Well, it's not quite fixed. 

If you have a PST file on the pool, it will BSOD on the new version. 
Guess how I figured that out.

[hollidayjr 0]

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

[Christopher (Drashna) 632]

Lol, yup.  as soon as i load Outlook, it would trigger a BSOD. 

This is fixed in 903 though.   so it should be good to go.