New or Updated in June 2018

It was inevitable but as I worked my way through a succession of Windows 10 releases to track the development of some feature whose write-up is ever more imminent, I just had to look for how and when Microsoft fixed the long-lived kernel bug that can crash Windows from user mode and which I reported to Microsoft in late December 2016 and published here in January 2017 when I concluded that Microsoft was insufficiently responsive. (For my take on that, see Most Viewed in January 2017.)

Surely not inevitable is that of the two simple coding errors that independently can cause the same crash, the 1703 release of Windows 10 fixes only one. An immediate consequence is that it remains true that all known versions of Windows can be crashed by one small unprivileged user-mode program. Almost as immediate is that I’ve had to update most of my own pages that describe not just the bug but the relevant functionality (the study and documentation of which was, after all, how the bug ever got found).

Tacked on, not quite as an after-thought, are two pages of user-mode cataloguing that I prepared in February as background to fixing for myself what is for me one of the bigger user-interface irritations of modern Windows. As noted in November 2017, there’s much such stuff to do before I can see myself using Windows 10 comfortably. More will come.

Kernel-Mode Windows

Shell