We have been informed about a problem with one of the recent Windows Updates, which causes technical issues with Identity Cloaker version 2. At this time there is only limited information about the problem available.

Symptoms: During the launch process of the application, the application fails to start with error message “Remote procedure call failed”.

The crash, however, seems to happen randomly and may be difficult to replicate. Additionally, connecting to servers may take longer than usual and the IP address may not be changed the first time you connect.

Solution: If you experience the above mentioned problems, we strongly suggest you download and install Identity Cloaker Portable instead.

I apologize for the inconvenience, we are working on a fix as we speak.

UPDATE 1:

We have been able to find the culprit – it is Microsoft Security Essentials. Once the real time protection is disabled, Identity Cloaker version 2 starts working properly again. However, disabling Microsoft Security Essentials is, of course, not advised. We will be communicating with Microsoft and I will update this blog post once we have more information.

UPDATE 2:

We are currently communicating with Microsoft.

A perhaps imperfect but functional solution:

In the MS Security Essentials, add an “exception” for the whole Identity Cloaker application folder. Please see this Microsoft howto and in the “File Locations” field enter “C:\Program Files (x86)\Identity Cloaker” (without quotes), click Add and Save Changes.

We will also have an update for Identity Cloaker that will automate this process, later Today.