The hazard with using any kind of tuner or performance enhancer that changes multiple settings is that every setting is a variable in the equation. If something goes wrong it can take a long time to track it down. It almost forces you to take a system snapshot and just back it off if something doesn't fix in a short time. Like an hour or so.
For this reason I do not install updates to the OS unless I have a specific problem and find an update that fixes it. The only exception I make is service packs. At least there is some effort to test after installing the service pack to see that all the fixes play together nicely. With weekly bundles of updates there's no time for testing.
-MilesAhead
This is true, and we were aware of this before deciding to go public with the project. That's why the focus has always been on leaving the smallest possible footprint, meaning it's literally impossible to fuck up your PC using Blackbird beyond minor annoyances, which were all resolved quickly through our tech support mail -
[email protected] - on a case-by-case basis.
Since November 2015 there have been a total of 8 issues raised through contacting us. All were resolved and fixed, if needed, in later Blackbird versions.
You can never use Blackbird and wind up not booting to your desktop on whatever version or edition of Windows you may run.
Maybe there's a slight chance of that happening when Blackbird removed KB updates and Windows is being rebooted/configuring updates while power is suddenly lost.. but that has never been reported or confirmed, just guessing here.
But we do encourage the use of snapshots, it's a smart move and its better to be safe than sorry.
This morning the problem was back!! :o
Hmm... Windows was open, but Explorer kept freezing. Suddenly it occurred to me that the only thing changed from the day before, should be time; the clock, and it was still displaying Windows' default clock, not my third-party T-Clock 2010! When I finally could enter Explorer, I looked into Outpost Security Center and realized that T-Clock wasn't mentioned anywhere in Outpost. Of course it should be, so I navigated Outpost to the file and clicked "Allow". I cannot tell until tomorrow if this has cured the patient - but I expect it has.
-Curt
Keep us updated, if the problem persists don't hesitate to contact us, we got your back.
