Re: Windows Defender Keeps Killing My App
- From: "Nobody" <nobody@xxxxxxxxxx>
- Date: Mon, 5 Oct 2009 10:08:27 -0400
"Mr. Taco" <mrtaco@xxxxxxxxxxxxx> wrote in message
news:%23BlZxGWRKHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
I wrote a fairly simple windows service that checks a website and
returns the status, emails me if the site is down. Works fine in XP (of
course), but windows defender in vista labels it as "Alert Type:
Unclassified software" and "takes action against it".
I've modified the app manifest to require admin, highest avail and
invoker, but it's not helping anything. In my travels, I glossed over
some idea where I would have to start the service with a "runas" - I
have no idea what that is or where to begin with that.
I've been using the VS command line and the installutil to install the
service for testing.
Anyway, if someone could tell me what the best practice is to deploy a
windows service on vista, I would appreciate it.
I don't use VB.Net, but made services in VC6. It's possible that you are
running it as a regular application(Some services have command line options
for debugging or testing). Instead of running the service directly using
Explorer, use the Services applet in Control Panel to start it. Also, in the
"Log On" tab, check which account that the service is using, you can change
it if you want to. Installation tools internally use CreateService() API
function and the last two parameters specify the account to use. You can
decide what account to use at install time, or change it later using the
Services applet.
Finally, one of the changes in Vista and after is that services run in their
own session for security reasons, called session 0, which is non
interactive, so you can't use things like
FindWindow/EnumWindows/SendMessage/PostMessage to talk to the service from a
GUI app. If you need to make a software that configures the service, you
have to make a second EXE and communicate with the service using some
mechanism, such as named pipes, winsock, or the registry.
See this article:
Application Compatibility: Session 0 Isolation
http://msdn.microsoft.com/en-us/library/bb756986.aspx
This is what Session 0 Isolation is trying to prevent(Look for "WM_TIMER"
and "Session 0"):
http://en.wikipedia.org/wiki/Shatter_attack
.
- References:
- Windows Defender Keeps Killing My App
- From: Mr. Taco
- Windows Defender Keeps Killing My App
- Prev by Date: Re: Debugger Stepping into everything
- Next by Date: Re: Control arrays and FormN.Label31
- Previous by thread: Re: Windows Defender Keeps Killing My App
- Next by thread: Re: Windows Defender Keeps Killing My App
- Index(es):
Relevant Pages
|
