Autopatcher.net

I've encountered it a couple of times before, but always on systems that had other issues (e.g. malware). With those, I just went with the nuclear option (format and re-install). I didn't figure there was any point reporting it here, because it was obviously not an Autopatcher issue. This was the fi...

Very cool! Can't wait for the next build, even though it means I'll have to devise some other test to see if the GUID problem exists on a system.

I'm not sure if that's good news or bad - at least when Autopatcher failed, I knew there WAS a problem!

Out of curiosity, in what way is it better? I mean, other than the whole GUID issue, that is. Is there a performance increase, like the MSN article hinted at?

Sometime it sucks to be the "expert" on hand, doesn't it? Been there! LOL!

What I meant to say is that I don't know enough about the Crypto API to say whether or not switching away from private keys is the right answer. In fact, I never really looked at the API until yesterday, and even then it was only enough to create a little C++ app to reproduce the issue simply and re...

ADDENDUM: (Highly) Technical information for the Autopatcher developers, the curious, and (hopefully) for search engines to lead people with similar issues to the solution! :D The symptom of the problem was the CryptAcquireContext API was failing with conflicting errors. Looking at Microsoft's samp...

I'm posting this here so that maybe someone can benefit from my efforts over the past two days to debug this issue. :roll: Here's the exact error I was getting every time I launched AutoPatcher on a problematic system: Where: HashModule.HashFile() At Line 116 Error Code: 0x1: Failed to acquire crypt...