Dokan Error: CreateFile failed with error 433

[snashikkar11]

Hello Dokany Team

I am seeing following errors in the Dokany debug logs when I create a Dokany share for SMB share created using NetShareAdd.

index=1
Dokan: debug mode on
Dokan: use stderr
AllocationUnitSize: 512 SectorSize: 512
device opened
CreateMountPoint C:\Program Files\mount\test_smb -> \??\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}\ success
Dokan Error: CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433
Dokan Error: CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433
Failed to open keepalive file: \\?\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}\__drive_fs_keepalive
Enable legacy keepalive.
Dokan Error: CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433
Dokan Error: CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433
Dokan Error: CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433
mounted: C:\Program Files\mount\test_smb -> \Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}
Dokan Error: DokanKeepAlive CreateFile failed \\.\Volume{d6cc17c5-1735-4085-bce7-964f1e9f5de9}: 433

Any idea why dokany is seeing Error 433 for the volume while querying volume info? What does that signify?
Eventually it logs mounted: but in application I observe the share is immediately unmounted after mount.
Appreciate your help if we can provide some more insights into why we could see this behavior with Dokany.

Thanks
Sandeep

[Liryna]

It seems like the userland application isn't capable of opening to virtual drive created by the kernel driver. This could happen if a filter driver like an antivirus is blocking the application to access it and return 433 ERROR_NO_SUCH_DEVICE. The device is unmouted since the application couldn't communicate with the virtual drive in time.

You can use fltmc filters command to get a list of possible filter driver culprit.

[snashikkar11]

Thanks for your help. I appreciate. Will check.

Thanks
Sandeep