Coincidence? I Think Not. Nefarious? Not Necessarily
Hugh Hewitt
Tue, Nov 17, 2026
By Hugh Hewitt, Townhall.com
More tech failures yesterday – banks and one airline. After last Friday’s fails, one has to wonder – are these some sort of cyber probing attacks? The banking fail in particular is very frightening. Never forget Leroy Jethro Gibbs Rule #39, “There is no such thing as a coincidence.” (If you have never watched “NCIS” and therefore do not understand what I just said – it’s in reruns everywhere, catch-up and thank me later.) Too many failures too close together to easily write this whole thing off to coincidence. It just sits there and niggles at the back of your mind. Well, it is possible that these things are not coincidental, and yet they are not the product of an attack of some sort.
Last week, Microsoft issued a security patch to Windows 11. And now some of my very important software will not run. Every time I want to run that software I have to uninstall that update. Of course, the next night Microsoft automatically reinstalls the update. I am stuck with two companies Microsoft, maker of the operating system, and the company that produces the software app pointing fingers at each other while I have to diddle with it several times a week when I need to use that program. They will eventually work it out and things will eventually return to normal, but it sure is a pain in the neck for now. And it happened coincidentally with these major systemic fails and it got me thinking.
The, last night DHS’ Markwayne Mullin appeared on Hannity and blamed all these fails on something that seems remarkably like what happened to me. Mullin blames new “SI” software. I have no idea what the term “SI” means and a little googling is no help. But as Mullin goes on he is talking about “self-healing software.” That is software that can fix its own bugs. It is a very limited form of AI.
So, let’s go back to what is happening with me. Windows 11 is the “operating system” – it controls the basics of how the computer operates, drives, internet connections, manages memory – it manages the resources the computer has to offer. Apps, or applications, do specific things the user wants and are constantly communicating with the operating system for the computer resources they need. For decades now, when the makers of the operating system wanted to update it, they had to tell all the makers of apps about the upgrades so they had a chance to respond and make adjustments to their apps so the apps and the operating system could continue to talk to each other. But when the operating system can change itself, well, that robs the app makers of the opportunity to adjust in a timely fashion.
Now in my case it was simply a matter of poor communication between Microsoft and the maker of my app of concern. Mullin is saying on these big systems it is basically the same thing, but it is happening inside the computer, much faster than when people had to launch the updates.
Mullin’s explanation makes sense to me – particularly in light of what I have experienced of late. We are, in this case, our own worst enemy. We have rushed these self-healing systems into use without fully examining the ramifications of their implementation. So, these major fails are not coincidental – they share a common causation. But they are not nefarious. They are in fact a pretty common human fail. And so my initial instincts were right. Tech creates a greater need for us to be reliable people.