somebody help me please!!!

  • Thread starter Thread starter lee pearman
  • Start date Start date
L

lee pearman

I am extremely disappointed to receive no
support whatsoever from either GIANT Company or Microsoft
with regards to solving a critical 101 error i get when
trying to load up "giant antispyware".

Giant tell me that my problem is with microsoft as i
apparently have microsofts beta version of AS even after
i tell them they are wrong and that i purchased the
program from them in november 2004 (ie. before december
2004) therefore i NEVER downloaded the beta version of AS
from microsoft because on their website it says not to if
you currently are a subscriber of their product, and I
guess having the program installed in C:\Program
Files\GIANT Company Software\GIANT AntiSpyware directory
is a sure sign that im not talking BS, however now they
just ignore my messages when i tell them this. my last
email that i have got from them said this:

"Thank you for contacting GIANT Company Software, Inc.

You have filed a report to indicate you received an
error message when trying to use BETA Microsoft Windows
Anti-Spyware. We apologize for any inconvenience you may
have experienced however Microsoft Windows AntiSpyware is
a BETA product and is not supported through this alias.
The error you received pointed you to this alias in
error. BETA support for the Microsoft Windows AntiSpyware
solution is available through the following Microsoft
Newsgroup:

http://communities.microsoft.com/newsgroups/default.asp?
ICP=spyware&sLCID=us

If you have any other questions or comments please feel
free to contact us at anytime.

Thank you,
GIANT Company Software, Inc.

In case this email does not fully answer your question,
or you would like to contact us for any reason, simply
reply to this email."

A complete and utter cop-out as far as i am concerned and
this just highlights how untransparent the support is
between the actual makers in the first place of the
antispyware product and the beasts who jumped on the
bandwagon to take it over and make it theirs.
And before you say that this critical error problem has
been answered in a previous thread, well i do already
know this because i can actually read!!, but the
workaround did absolutely bugger all for me. I am
starting to believe that this whole AntiSpyware lark is
just a red herring and that really nobody knows/cares
what the hell is going on with either
product (be it from Giant or BETA-microsoft - and this is
especially confounded since the microsoft takeover)
At least i had the program running problem free for 3
months until they did takeover - so i guess its not
really Giants fault. They were much, much better when
they were on their own. All it is now is utter confusion
and passing the buck.
so bollox to all this, i cant be bothered anymore.

from a very disgruntled customer.
 
Microsoft, via the support links at Giant's site is contractually obligated
to help you.

We have a fix posted here for error 101 issues as they relate to Microsoft
(beta) Antispyware.

I'm somewhat hesitant to post that for you because I've no idea whether it
is relevant to your issue--however, I think it shouldn't be harmful, so here
it is:

I must emphasize that very few if any of us have ever seen the Giant
product--and that the support links through the original site are your best
bet for accurate advice. I'm very sorry to hear that they aren't
responsive--I expect better from Microsoft, as you do.

-----------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Well thanks for your reply Bill. At long last somebody is
responding!!...anyway as i said before, i can read and
have tried your workaround fix before but to no avail. It
doesnt solve the problem in any way. However i have today
received a response from support at GiantCompany which
now reads:

"Thank you for contacting GIANT Company Software, Inc.

I apologize for the issue you are experiencing, We have
an update to the software that I believe fixes the issues
you are having.
To upgrade, please download the latest version of Giant
AntiSpyware at:

http://www.giantcompany.com/downloadFile.aspx?prodID=70

You will need your registration key. You can have your
user name and GIANT Antipsyware registration key from the
following link

http://www.giantcompany.com/forgotInfo.aspx?prodID=70

Please let us know if you have any trouble with our lost
key page.

If you have any other questions or comments please feel
free to contact us at anytime.

Thank you,
GIANT Company Software, Inc.

In case this email does not fully answer your question,
or you would like to contact us for any reason, simply
reply to this email."

So i guess they have finally acknowledged that i do have
their product as i sent them my diagnostics and error
logs. I will try what they say one last time but im
pretty sure that the link they have quoted is just the
same link i go to from their website for redownloading
and reinstalling their product (which i have im sorry to
have to say I have already tried and it doesnt solve the
problem either - still get error 101 upon attempting to
open the product.

As a side, perhaps i could send my diagnostics and error
logs to you to check out if you tell me where to send
them.

Thanks again for replying at least!

Lee
-----Original Message-----
Microsoft, via the support links at Giant's site is contractually obligated
to help you.

We have a fix posted here for error 101 issues as they relate to Microsoft
(beta) Antispyware.

I'm somewhat hesitant to post that for you because I've no idea whether it
is relevant to your issue--however, I think it shouldn't be harmful, so here
it is:

I must emphasize that very few if any of us have ever seen the Giant
product--and that the support links through the original site are your best
bet for accurate advice. I'm very sorry to hear that they aren't
responsive--I expect better from Microsoft, as you do.

-----------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I am extremely disappointed to receive no
support whatsoever from either GIANT Company or Microsoft
with regards to solving a critical 101 error i get when
trying to load up "giant antispyware".

Giant tell me that my problem is with microsoft as i
apparently have microsofts beta version of AS even after
i tell them they are wrong and that i purchased the
program from them in november 2004 (ie. before december
2004) therefore i NEVER downloaded the beta version of AS
from microsoft because on their website it says not to if
you currently are a subscriber of their product, and I
guess having the program installed in C:\Program
Files\GIANT Company Software\GIANT AntiSpyware directory
is a sure sign that im not talking BS, however now they
just ignore my messages when i tell them this. my last
email that i have got from them said this:

"Thank you for contacting GIANT Company Software, Inc.

You have filed a report to indicate you received an
error message when trying to use BETA Microsoft Windows
Anti-Spyware. We apologize for any inconvenience you may
have experienced however Microsoft Windows AntiSpyware is
a BETA product and is not supported through this alias.
The error you received pointed you to this alias in
error. BETA support for the Microsoft Windows AntiSpyware
solution is available through the following Microsoft
Newsgroup:

http://communities.microsoft.com/newsgroups/default.asp?
ICP=spyware&sLCID=us

If you have any other questions or comments please feel
free to contact us at anytime.

Thank you,
GIANT Company Software, Inc.

In case this email does not fully answer your question,
or you would like to contact us for any reason, simply
reply to this email."

A complete and utter cop-out as far as i am concerned and
this just highlights how untransparent the support is
between the actual makers in the first place of the
antispyware product and the beasts who jumped on the
bandwagon to take it over and make it theirs.
And before you say that this critical error problem has
been answered in a previous thread, well i do already
know this because i can actually read!!, but the
workaround did absolutely bugger all for me. I am
starting to believe that this whole AntiSpyware lark is
just a red herring and that really nobody knows/cares
what the hell is going on with either
product (be it from Giant or BETA-microsoft - and this is
especially confounded since the microsoft takeover)
At least i had the program running problem free for 3
months until they did takeover - so i guess its not
really Giants fault. They were much, much better when
they were on their own. All it is now is utter confusion
and passing the buck.
so bollox to all this, i cant be bothered anymore.

from a very disgruntled customer.
Click to expand...


.
Click to expand...
 
Back
Top