This issue is a regression of the following issue.
Click Here
This was re-introduced in V4.00 and resolved in V4.02.