My problem is that it's actually not all that hard to believe if enough money is put in the right hands.
Even if they use the heart of Windows 2000, they are still using an application that is designed to do a different job. When we burned stuff on Proms, when you needed to upgrade, you just altered the Rom core file, reburnt it and mounted it where the old Prom was. Because packets were identified by their destination, and saturation sent to the system, even if the hard-connection to the launcher was damaged, as long as something shared a link between the two systems they could share data. The system was more-or-less unaffectable externally and was easy to fix, even in combat situation.
Windows is not designed to handle that kind of thing, obviously things have updated since we used to program in Z80 onto Programmable Roms, but the theory remains the same, if an error occurs with someone elses program, and we tweak something and it doesn't happen again, it doesn't always mean it's fixed permanently, we've all encountered the problem of 'pointless error', where the computer crashes because 'it feels like it'. The more complex and indirect the code base is, the more chance there is for that error. Whereas hard-coding tends to either work or not work.