WGATRAY ... does someone know on valid system

  • Thread starter Thread starter Larry Gardner
  • Start date Start date
L

Larry Gardner

I have a problem. Each time I logon my system as Admin, the system
autoconnects using wgatray.exe.
I have used WGA Diagnostics tools, gone to MS Web-site and checked with
on-line Genuine Advantage ...
and I still connect each time I login.

I do not get any nag screen ... because my system is Genuine ... it just
connects out. And then the connection stays open.

If I logout and login multiple times throughout the day ... it continues to
connect.

Is some file not being updated.

I eventually renamed the wgatray.exe file in system2 and system32/dllcahe.
But I want this to work the way it's supposed to.
It makes me wonder if something is not coonfigured correctly.

I have two other systems ... and I don't have this problem and they
work/check out fine.

This is the only system with a MSDN subscription version installed ... but
like I said ... I get no validation errors.
 
The current WGA notification app--of which wgatray is a part--connects far
more frequently than many users would like. Look for an update to this
soon, I think. This has gotten some press lately, and Microsoft has said
they will change the behavior.
 
I may have solved the problem ... by removing the data.dat file and going to
www.microsoft.com/genuine and re-validating XP Pro and Office XP.
Both were successful ... I rebooted ... after putting the wgatray.exe back.

I'll keep monitoring this.

However, the system should not be auto-connecting ANYTIME on a dial-up
connection. Our small company has to pay for each connection.
The dial-up caused by wgatray.exe is performed after you login ... and prior
to processes started and executed. So by the time the system gets
around redrawing the desktop with the Welcome Screen, you are already deep
into connection. And then it leaves it open.

This should not be done at a login screen ... maybe when you connect to the
network ... it should double check ... or when you perform a Microsoft
Update.
The user could be notified then ... and configure the system to nag without
continuing to connect at login.

The reason they did this ... is to prevent Firewalls from blocking
WGATRAY.EXE from being blocked. This supercedes most Firewall settings ...
even Microsoft's.
 
FWIW, the Windows Genuine Notification code which creates WGATRAY is now
released code, and I believe that the extraneous connection behavior should
now be gone in the released version--that's what I've seen reported, at any
rate.

--
 
Back
Top