IObitUnlocker Portable v1.1.2 - IObitUnlocker.sys File Not Digitally Signed

Initially I, and lot of other users, stopped updating Win7 when Microsoft started auto-updating folks to get Win10. When MS were in the game of the Win10 update they also started including lots of so-called 'telemetry' stuff in their updates. Of course, 'telemetry' is just another (supposed to be innocuous) term for 'spyware'. Microsoft's attitude was when all this kicked off, and still is, your data is our data. Sod that for a laugh. They are literally installing a spyware-suite onto users systems and claiming it's an operating system.

While all this messing around from Microsoft's end was going on a fair number of the more knowledgeable computer users started trying to vet what updates would get installed to their systems (to avoid Win10 and to avoid the spyware). They were doing things like 'hiding' update 'x' (actually multiples of them, 'a', 'b', 'c' . . . and so on) on the Microsoft update site to avoid downloading and installing it. Result of that was that Microsoft started, of their own account, unhiding some of the updates the users had hidden (in the hope that users wouldn't notice) and download and install. Other trick they got up to was to start re-labelling update 'x' to something else -- another attempt at trying to subvert users avoiding the so-called 'telemetry' stuff. Another trick they got up to was amalgamating update 'x' (which users didn't want) into update 'y' -- again trying to push their spy-ware onto users -- the magical 'cumulative' update with added spyware shoved in for free. They were also marking updates that self-evidently weren't 'critical' (though I believe they've change that category label now) into that category and tried punting their spyware that way. They were also backporting spyware intended for Win10 to be used on Win7 systems -- get the picture. This sort of behaviour on the part of Microsoft is well documented in forums.

Once I cottoned on to the sheer extent and sinisterness of all this that was it for me. Clean install of Win7 SP1 and no updates unless truly, utterly, essential -- I sure ain't the only one that did that. System is rock-solid no problems, this SHA signing issue is the only thing so far that has forced me to do an update.

Lastly, when you say 'outdated' system that is a pretty loaded term. What is 'outdated' about a system that works just fine? Also when you say why run 'insecure' you're using a loaded term and failing to see part of what and who the enemy is that you want to protect yourself from. See, 'insecure' would nowadays have to include am I secured against Microsoft. If you do automatic updates then the answer to that is a definite, No! If you are doing automatic updates then you are quite literally loading your system into a state of insecurity. I'm not kidding. The only possible way out of this would be to manually vet every update Microsoft offer, and let's face it the information that Microsoft supplies to users on what exactly update 'x', 'y' and 'z' are is very often opaque to say the least. Knowledgeable people on forums are attempting this and, to my way of thinking, tying themselves in knots in doing so. For me, I don't want to have spend hours of my life vetting Microsoft updates, the easy way out is base install and only update if totally essential. There are a lot of people out here that nowadays think exactly the same way. Microsoft stopped playing by the rules quite some time ago -- to avoid noticing that is true folly. They want your data, and they are getting it, by hook or by crook. 'Telemetry' -- really!