It’s more likely to be due to those windows being ‘somewhere else’ in the windbg workspace associated with debugging that particular machine.
You could try clicking ‘Clear Workspace’ on the File menu when you have the workspace open; this will lose the existing pane settings, which (hopefully) will bring them where you can see them again.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-596705- xxxxx@lists.osr.com] On Behalf Of Andrey Bazhan
Sent: 27 November 2015 10:09
To: Kernel Debugging Interest List
Subject: Re:[windbg] memory, assembly, scratchpad windows not showing
On Windows 8.1 host works fine.
wrote in message news:xxxxx@windbg…
I can no longer open these windows, its windbg 6.12.0002.633
debugging windows 10 x86. windows 7 64 is the host.
I have never had any problems with it before, perhaps its broken by
one of the massive glut of windows updates recently. Anyone else
seeing this?
Does it happen on a newer version of Windbg? 6.12.* is pretty old.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Monday, November 30, 2015 3:38 AM
To: Kernel Debugging Interest List Subject: RE:[windbg] memory, assembly, scratchpad windows not showing
Still broken. Rebooted the host this morning and its still screwed.
Oddly doing an undock all by a dock all makes them visible, and also doing a tile does.
Weird. The number of ways in which windows can go wrong never ceases to amaze me.