Microsoft confirmed the issue on June 18 and said a fix would not arrive until July 14. The company attributed the bug to a security hardening change that closed a 23-year-old unchecked-buffer vulnerability in the Windows Shell’s desktop.ini processor.
Inspiring confidence!