Verifier low resource, what went wrong

So I installed an older OS, actually server 2008 R2, hoping its low resource simulation might work better and discovered this:

It only has one Low Resource feature, like WIn7, but it has a manager UI to set the failure rate etc like Win10s Randomised Low Resource.

But it also worked like Win10s Randomised Low Resource. Ie, it failed the same request over and over again and is entirely useless.

So something clearly got messed up here. The basic low resource, which was working in a nice systematic way, got screwed around with on 2008R2 with the addition of some settings, and ended up useless and broken.

MSFT realised this for win10, and tried to put back in the working low resource, calling it ‘systematic’ and renaming the broken and useless one ‘randomised’.

However they failed to put back in the old working low resource, AKA ‘systematic’, one resulting in two entirely useless features.

Shame, MSFT used to not play around with the kernel and drivers, adding useless features and breaking stuff, that was the domain of the Office people, and of course the shell UI team. Seems things have changed.

What next, a broken and useless Windbg?

Dear oh god, the thought of that going wrong…

This is a by-product of the closed source model. Instead of getting a feedback from the developers community MSFT isolated itself.

IMO it is a by-product of not knowing when to stop putting paint on.

Some things, live valve amps for guitars (tube amps to the US guys) just don’t get any better, and are best just left alone. You can throw al the transistors and digital you like at it, but you aren’t ever going to beat a valve amp sound.