Thank you for bringing this issue to our attention. After careful consideration, we will be closing the 6000.2.X port as this issue will be resolved in a newer release. This decision is determined by factors such as severity, frequency of the issue, and the number of users affected by it. For more details, please refer to the latest port related to this issue. We apologize for any inconvenience this may cause and appreciate your understanding.