v4.0.1 did not have any relevant fix for this problem (not even sure why it was released). You’ll have to wait for a potential v4.0.2 that includes driver v15.0.3.
v4.0.1 did not have any relevant fix for this problem (not even sure why it was released). You’ll have to wait for a potential v4.0.2 that includes driver v15.0.3.