How is that not an F3 issue? As I am aware it had not happened prior to this release. This release is great and the work that has been done is phenomenal and some issues will arise.
I worked around the issue by adding it to the "none" group, thus hiding it from view.