Still not sure why it's suddenly having that issue on Win10 though. Apparently in IE, however, window's parent is NEVER itself. Could an Adobe employee confirm that the problem is getting solved and will be included in the next Adobe Reader update?