W7 has taken a disliking to a program

You are, I hope, joking?

I don't think that joke is in very good taste as it might give someone the idea that if you know what you're doing you can turn off UAC.

Just in case anyone thinks you were being serious here is a quick scenario to demonstrate just why even the most experienced user (unless they never download anything) should not turn off UAC.

EU is reading a forum and someone mentions a little utility that EU thinks would be extremely useful. EU does a google on the name of the utility and it doesn't come up with any warnings.

EU (who has previously turned of UAC because, after all, he's an EU and knows what he's doing ) downloads the utility which has recently become infected with some malware.

EU runs the utility and, because EU's turned off UAC, the malware silently makes changes to his system. Disaster ensues.

It wasn't defender because I temporarily turned it off and the problem remained.

And yes, I rather suspect that UAC has got it on its 'hit list'.

Just hoping that someone will actually know what's going on. It's not a problem for me in this instance because there is an easy work around but this behaviour may become a problem to either myself or someone else at some stage so I thought it would be a good idea to see if anyone has a definite answer.

But, please, people, stop suggesting that turning UAC off is an intelligent way to respond to a problem such as this. I'm sure most of us have seen at least one film where someone has gained access to somewhere they weren't wanted by causing an alarm to keep going off until someone disabled the security system thus allowing them access.

 

Same as before. (Remember that it behaves like that even when 'start.exe' is just a renamed text file with 'hello' in it.)

 

As I've said, there is a simple and 100% effective workaround so it's no hassle whatsoever.

There is still a possibility that someone who actually knows what's going on will see this thread and answer.

W7 has not been out that long so I would not be at all surprised to see this crop up again.

 

i had a program that did the same,e as this, but i set it compatibility mode to windows server 2003 (service pack 1) and that seemed to have sorted the problem