Hi Loren,
Let me try that again. I'm stevej at pmFAQtory dotc om.
Regarding seeing the PBT_APMPOWERSTATUSCHANGE messages, we use Microsoft Spy++, which is part of Visual Studio: https://msdn.microsoft.com/en-us/library/aa242713(v=vs.60).aspx.
Generally, there is no such thing as a perfectly flat direct current waveform. The power delivered isn't a steady x watts, but an average from a sinusoidal signal. Whenever you have a Surface power supply plugged into a power source, it's rectifying the signal. It takes a sinusoidal signal from a wall outlet and flattens it out. Think of taking the absolute value of a flattened sinusoidal wave. It still oscillates. You can also have a noisy signal due to weak shielding. Minor voltage spikes can occur. Whether such a real-world, as opposed to ideal, direct current could somehow trigger the Surface power circuits and OS to think that erroneous power state changes (however Microsoft defines those) are occurring is anyone's guess. What could give us some valuable data is for an electrical engineer who works with power supplies to put a (believed to be) defective power supply on a digital oscilloscope, monitor the waveform, and simultaneously monitor power-related events and messages in Spy++ to see what, if any, correlation there is.
This bug could be the result of an interaction among the power supply, the Surface battery (or batteries, in the case of the Surface Book), and the power management code, whether firmware or the OS (including drivers). As Erwin Ried pointed out, to us, the Surface is just a black box. We can see what happens when we make changes, such as swapping out a power supply, or disabling the ACPI-Compliant Battery Control Method driver, but our ability to delve deeper is limited by tool limitations and not knowing much about the Surface architecture, both hardware and software. We can only do so much. At some point, Microsoft has to figure the rest out.
Our goal is to make clear to Microsoft that there is a real problem, to get them to take action, because this bug is a Windows usability show stopper. This bug has a very long (i.e. years of) history, and Microsoft has never formally acknowledged it. There have been a lot of suggestions as to what to do, from workarounds (such as disabling the ACPI driver, which could lead to overcharging and damaging batteries and disables power management functionality such as time remaining) to swapping out power supplies (which has worked for three people that I'm aware of so far).
The most promising advance we've made to help Microsoft, so far, has been identifying that PBT_APMPOWERSTATUSCHANGE messages cause thumbnail previews to disappear. So, we've been tracking serial numbers of (believed to be) defective power supplies, as well as good ones, on the assumption that it really is defective power supplies that are causing this problem, but this is a tentative conclusion pending further evidence. One experiment that I'd love to try with your SB is to send you this 65W Microsoft power supply, which works perfectly for me on my SP4, to see if you still have #ThumbnailPreviewsDisappear while both your batteries are 100% charged and your SB is plugged in (or under any other circumstances). If you do, then that would give us invaluable information: we'd definitively know that it's not (just) the power supply.
Thanks,
Steve