Blank window?

  • Thread starter Thread starter Bill Evans
  • Start date Start date
B

Bill Evans

Running Xp Home SP2/ Norton Systemworks including Norton AV. installed
fine and it ran fine for a while, Some areas it still does, it does the
scheduled scan every evening, and I currently have one item waiting for my
attention. However, when I click on the item to deal with it, the Window
for Antispyware loses all text, graphics etc, I only have the Window with
the "sky effect" in the background. Same thing for startup screen, and
several others. Some of them show. Most don't. I tried to change/uninstall
but get a message "The installation package cannot be opened. Verfiy the
package exists, and that you can access it. or contact the vendor to verfiy
this is a valis Windows installer package."

Any ideas?
 
Bill,

There is a known issue with MSAS and NSW. It's your choice of which one
you want to uninstall. I suspect that NSW needs an update, but that's
just my opinion.

Steve Wechsler (akaMowGreen)
MS-MVP 2004-2005
Windows Server - Software Distribution
Windows - Security
 
I disagree with Steve about this issue. There may be a
bug with NSW, but we also have the same issues running
Norton Corporate Edition 9.0 and Norton 2003. Yet other
machines on our network running the same software run the
program fine. Is there anything else that we can try to
attempt to resolve this issue? I hope that it will not
involve removing my Antivirus protection in order to run
your BETA sofware.
 
Here's something to try. At this point, I would call it snake oil--there's
no evidence that it will help your issue. However, it should be harmless
snake oil, and if you aren't on a dialup, it won't take too much effort to
test--there's a reboot involved, as I recall:

http://www.microsoft.com/downloads/...61-7a9c-43e7-9117-f673077ffb3c&DisplayLang=en

This is Service Pack 6 for the VB6 Runtime. The runtime is apparently made
up of a number of files. If these files somehow become version soup--i.e.
of different versions--there can be issues with registration of .dll files
on installation--these should be visible in errors.log, and I can't cite all
the possible effects of such issues--hence this recommendation!

Applying this (or even an earlier SP) should bring all the files to like
versions which may allow the install to complete properly.

Please let me know what happens, and if I've wasted your time!

FWIW: Microsoft is aware of compatibility issues in this beta, and is
actively investigating such issues, including those with Norton software.
 
Dale,

Did not know there were any issues with NAV ... Recommend you do NOT
uninstall AV software in favor of a beta product. Sorry if I did not
make that clear.
However, have seen issues with Symantec products that makes one want to
seek other security programs. Have not had the same issues with AVG,
eTrust, KAV, Avast, etc. So can only draw the conclusion that the issue
does NOT stem from the OS, but from the software.
YMMV ...

Steve Wechsler (akaMowGreen)
Windows Server - Software Distribution
Windows - Security

==============
*-343-* FDNY
Never Forgotten
===============
 
Bill,
I did have the same problem with blank windows and was
very happy finding your answer.
Actualy it inspires me to recheck the "errors.log" in the
app directory thate stated:
372::ln 5:Failed to load control 'RichTextBox' from
RICHTX32.OCX. Your version of RICHTX32.OCX may be
outdated. Make sure you are using the version of the
control that was provided with your
application.::GIANTAntiSpywareMain:ctlAgentsSummary:LoadDe
tails::4/11/2005 9:54:02 PM:XP:1.0.501
The file is located in System32, and I did an "regsvr32
richtx32.ocx" that solve the problem. It was not
neccesary to run VB update.
On my system i have NYS with NAV, but as you said this is
not the problem.
Maybe it will help.
Dani
 
Terrific--glad to hear you were able to spot the issue. I'm not tracking
well which issues I should ask the user to examine errors.log file for, I'm
afraid. It is possible that applying the SP would have been effective for
you as well--I'm unclear exactly why it happens that the installation
process is unsuccessful in registering a given file, but the user is able to
do it just fine later.
 
Back
Top