I believe Golden is alluding to an earlier post in his link where Eva Ting the OP mentions in Post #4
that this started after the August Patch Tuesday Updates. Later on in post #12 Gerard O'Brien mentions he sent an inquiry to Microsoft (MS) on 08152015 and the response a month later on 09032015 was:
>We?re aware of issues with recent Windows 7 symbols and are investigating the cause and possible solutions. We don?t have an ETA for a fix at this time. Thanks Microsoft.
Laith; Your discovery is only a work-around, the bigger problem is; This was caused by a windows scheduled update.
If MS does find a fix, your work-around may interfere with it on your machine. I'm not saying what you did is wrong; If it works, it works. But be alert down the road for dbg/system patches that mention, ntdll, kernel, .peb or .teb, you may have to fuss with those updates/fixes.
I did see Golden's link from OSR a month ago and thought I had posted about it, but I can not find any of my posts that mention it.
I did try going back and uninstalled several August updates, then tested the debugger with no joy, unfortunately I had to reserve myself for pressing family matters so I couldn't continue to see which update caused the problem so, I stopped. Me? I'm going to wait out MS and see if they do come up with a fix.