WinDBG symbols

We will have to wait and see if Laith has made any progress, as I understand he has W10 and is trying to read W7 dbg files with the same luck you just had, there is a symbol problem. It seems anyone that has any OS from 7 up to 10 can not read win7 dbg files.

You have 8.1 and can read dbg files from 8 up to 10, but not win7, right?
I'm with Derekimo and essenbe, this is an update problem that started after the 081115 patch Tuesday. One way, possibly, is to do a system restore to before that date to remove those updates to see if windbg functionality returns, I tested with removing a couple, KB3071756 and KB3060716, but it didn't help, I would go further but this is my main machine.

That's what I thought, thanks for confirming. Even if Laith had the newest win10SDK he wouldn't be able to read the 7 dbg files.

I seeing more sites with 7users asking "what's up with the symbol problem?". I fear that with the roll-out of 10 7users will be left behind until their concerns with the debugger become more than a trickle.

Take a look at how MS "handled" the KB3076895 problem.

good to hear!

The problem is bigger than just reading W7 symbols in W10.......
OSR's windbg List: recent windbg symbols not working

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.