First of all, I'll ask you not to form an opinion that I'm one of those supposedly self-serving StarForce haters until I'm done because I've found something very interesting about their drivers which is, in fact, reproducible. This is related to ProcessGuard too, so it's not in the wrong forum. Anyway, after having accidentally bought my first game with Star-Force embedded in it a couple of days back, I worked to manually remove its essence from my computer. I missed a couple of files though that aren't mentioned in most of the manual uninstallation instructions and thanks to that, it somehow managed to redistribute itself. Now having thought I'd uninstalled Star-Force, I thought I'd set myself up to protect myself from it via ProcessGuard. I added Protect.exe to the list and set it to Deny Always but just in case, I figured I'd add it to the security list for that extra level of protection. The moment I did this, I had a bluescreen. Apparently because I was 'tampering' with protect.exe, I don't know. I tried rebooting, bluescreen. The only thing I could do to stop it was renaming my ProcessGuard folder, via DOS, so that it wouldn't be there on reboot. That worked. I found the driver and I uninstalled it, this time making thouroughly sure that it's gone. I'm hoping that this time when I start ProcessGuard, it won't bluescreen, at least it shouldn't if I'm understanding this correctly. If it does though, how might I go about removing an entry from ProcessGuard's list without actually starting the application? Perhaps a way to wipe the configuration and start fresh, even? I ask this just in case I start up the program and I find myself with another bluescreen, I doubt I will but one never knows to be honest, I don't know what Star-Force is doing with its latest version so I don't trust them. I'll report back with what I find after I've tried it. As I said though, I invite anyone with a very recent Star-Force protected game (Dreamfall UK in my case) to install the game and then try adding Protect.exe to their security list. You won't even have to check any options, you won't have to tell it not to modify or anything like that. It's just the moment you select to add it from the context menu, poof, bluescreen! That's pretty damning evidence if you ask me. Anyway, I just wanted to let you guys know so you wouldn't fall into the same pit-trap. Bluescreens perturb me greatly because my PC, under normal circumstances (unless it's forced to) never crashes. Ever. I'm very careful about my software, I mostly go with open-source and I stay well away from malware and I keep myself protected with the best to ensure that aswell (most of the software mentioned in this forum, including the likes of Nod32). I think to force a computer to bluescreen under these conditions (and no, I didn't have any games open or running) is very wrong and to be honest, I wouldn't mind betting it's grounds for a legal suit to be filed against them by the developers of PG. Anyway, I won't say anything other than that, draw your own conclusions but please, before you dismiss me, try it yourself. --- Just to clarify; I'm using the latest (3.150) full version of ProcessGuard. I purchased it using the same email address that I used to sign up to this forum with. --- I hope I'll get at least some response to this anyway because I think that the probability that adding applications to PG's protection could cause an otherwise sturdy and unflappable computer -- which has never crashed in the time it's been running since its build -- to hard-lock simply by adding a process to its protection list is a disturbing prospect. Basically I'm just looking for some advice here. I did buy ProcessGuard and it might still hard-lock once I reactivate it. If you could at least tell me how I could remove the offending process, I'd be happy. I'm sorry to impose anyway, I know a lot of bad stuff has been said about Star-Force and I don't know what I can do to convince anyone I'm genuine. I'm just looking for help solving a problem here that I can't solve. I'd just like to know that if I do start PG again and it does hard-lock again (for the third or fourth time), I'll have a way to rectify the situation waiting for me. I'm pretty good with working with the registry andsoforth and I'm nothing to sneeze at as far as software configuration is concerned. That's why I'm wondering where the PG config information is stored, so I'll remove the right thing.