This message was posted on behalf of Intel Corporation
That's a known issue that has been reported before. Unfortunately, there isn't a complete fix for this yet, so the workaround suggested is the one described in the thread you linked.
I checked your recent post in the following thread: https://communities.intel.com/message/384472#384472. We appreciate your feedback on this. I'll pass the suggestion to the proper team so they can check it. Hopefully, a future release fixes this issue properly.