I certainly wished I had been aware of this before upgrading my father's computer to Windows 10. The upgrade implements the 1511 update now, so it has this problem. I had assumed it was a problem...