27 replies to this topic

[Labam]

Labam, on 07 February 2013 - 05:25 PM, said:

The reason is simply that I like to have the system on drive C: and all programs on drive D:

On my other computer mbam works perfectly on drive D:

...the other system is also Win 7 64bit.

[exile360]

Yeah, installing on another drive shouldn't be a problem. I suspect this is more related to permissions or something like that.

If you would, please open a support ticket on our helpdesk located here so that one of our support personnel can work with you directly to do a more advanced diagnosis of the system and hopefully find the solution.

[Labam]

exile360, on 07 February 2013 - 05:47 PM, said:

If you would, please open a support ticket on our helpdesk located here so that one of our support personnel can work with you directly to do a more advanced diagnosis of the system and hopefully find the solution.

Ok, done.

[exile360]

Labam, on 08 February 2013 - 03:07 AM, said:

Ok, done.

Excellent, thanks. And good luck, hopefully it won't take them long to track down the problem and get it working properly on that system for you.

[Labam]

Here is the answer from the support team from last Wednesday:

Quote

Keep working with the forum help.
We'll close this ticket, we cannot afford to use resources of two techs

Ok, understood.

[Labam]

Ok, problem was not fixed so I tried to find a solution on my own.

As I was the only one with this problem (at least nobody reported a similar story in this forum) I started to evaluate what is different on my system compared to the other environment where mbam was running well. On both systems I had some kind of a special setup for Windows 7 as I have moved the "C:\Program Files" and "C:\Program Files (x86)" folder to drive D instead of default drive C and on both systems I haven't faced a problem with installing new programs so far!

To make a long story short: I used two symbolic links for both folders (created with "mklink /j") on drive C pointing to the respective directories on drive D and left the registry settings in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion" still pointing to drive C (which usually works as every file or directory could be accessed with pathname C although it's physically on drive D). But some reason (?) mbam seems to have a problem with that so I changed the registry setting for all key like "ProgramFilesDir" and "ProgramFilesDir

[Labam]

Labam, on 20 February 2013 - 03:21 AM, said:

Ok, problem was not fixed so I tried to find a solution on my own. As I was the only one with this problem (at least nobody reported a similar story in this forum) I started to evaluate what is different on my system compared to the other environment where mbam was running well. On both systems I had some kind of a special setup for Windows 7 as I have moved the "C:\Program Files" and "C:\Program Files (x86)" folder to drive D instead of default drive C and on both systems I haven't faced a problem with installing new programs so far! To make a long story short: I used two symbolic links for both folders (created with "mklink /j") on drive C pointing to the respective directories on drive D and left the registry settings in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion" still pointing to drive C (which usually works as every file or directory could be accessed with pathname C although it's physically on drive D). But some reason (?) mbam seems to have a problem with that so I changed the registry setting for all key like "ProgramFilesDir" and "ProgramFilesDir

(x86)" to drive D and now everything works again.

[Firefox]

Sounds great, and thanks for getting back to us to let us know all is well now. Intresting setup you have going on there.... At least you found what the issue was, which looks like Malwarebytes does not like what your program "mklink /j" is doing.