Yeah, tested it on Windows 11 and Windows 10, same message. Maybe false detection or something else. I think I fixed it, thanks for the info
