Win2KPro Install Failure

  • Thread starter Thread starter PeterY
  • Start date Start date
P

PeterY

Has *anyone* installed successfully on Win2K Pro?
I get the same message as Daniel ("The windows installer
service could not be accessed...") trying to install
(after download) on my Win2k Pro standalone laptop (with
dialup internet access).
I've never had a problem with Windows Installer Services
for many other installations and my Add/Remove Programs
works fine. I'm running with full admin privileges... any
advice what I should do to install this beta?
Thanks,
Peter
 
I got it to install on Win2K no problem, check running
DLL's and make sure everything is regestered, also, do NOT
download it from "windows authentic program". click opt-
out.
 
What's your reasoning about not downloading via the "genuine" path?

It happens that I just did a successful install and run on a Windows 2000
Professional machine belonging to my mother in law.

In fact, i did just what you recommend. My reason was that I am 320 miles
from her machine, and I can't read the numbers off her Certificate at that
distance, and she's in the hospital getting a hip replaced.

However, I know of no reason not to go through the other route, and have
done that on other Windows 2000 machines. They have been servers, however.
 
Tuesday 11 January, 2005: Time: 0113 Hours CST (GMT-6
Hours) I have successfully loaded MICROSOFT ANTISPYWARE
BETA 1 to a total of 3 computers I own. Two of them use
WINDOWS 2000 PROFESSIONAL SERVICE PACK 4 and the other, a
laptop uses WINXP HOME. I had a problem with one of them
in that I had TURBOTAX 2004 installed which offers a
program known as ITSDEDUCTIBLE EXPRESS. This is an offer
to provide for $19.95 a program which helps you determine
how much sales tax was paid during 2004. I have rejected
this officer as the IRS offers publication 600 which
offers by state a number the IRS will accept without
question. This is a new deducation. I bought two new
autos during 2004 and paid over $4,000 in Illinois Sales
tax. This program ITSDEDUCTIBLE EXPRESS, caused a
conflict which took up 14 hours of my time to solve. Not
only that but it appears to be impossible to totally
delete it from the TURBO TAX PROGRAM and the Registry.
I had to finally uninstall TURBOTAX 2004 and then
reinstall MICROSOFT ANTISPYWARE BETA 1, which then ran as
it should. I notified TURBOTAX by going to their WEB SITE
and they have already contacted me by phone about this
problem. Do not call their 1-800 phone number as it
connects in India with a party who does not speak English
well, nor understand English well spoken. As I write this
both programs are working well. I still have SPYBOT
SEARCH AND DESTROY and AD-AWARE installed. MICROSOFT
ANTISPYWARE BETA 1 offers the option of either an
optional search of your system when you request it or
continuous background monitoring. I have elected to use
the search option so that it does not interfer with the
operations of SPYBOT SEARCH AND DESTROY AND AD-AWARE. Have
you downloaded all of the updates for WIN2000 offered on
the MICROSOFT WIN 2000 SITE? JOHNPAULJONES.
 
I'm glad you were finally able to persist and get the product installed.

I believe that the issue you ran into was caused by interactions between the
Windows Installer and the program you mention which was related to your tax
program.

Thanks for reporting the details, and again, congratulations for your
persistence and final success!
 
goto start -> run -> type "msiexec.exe /regserver" no
quotes. click ok. then try the install.

thanks,
-j
 
Thanks Jon, but this didn't work for me.

System seems to accept this command but without
acknowledgement and no chance to "click ok". I can't find
regserver as a documented arg for msiexec either... are we
missing a flag?

My symptoms remain:
-Install Shield Wizard for AntiSpyware gets to the
step "Configuring Windows Installer ..." and appears to
launch Windows Installer.
-Windows Installer sleeps for a while with
status "Preparing to Install..." After 30 seconds or so it
reports that:
"The windows installer service could not be accessed. This
can occur if you are running Windows in safe mode or if
windows installer is not correctly installed."

Peter
 
Back
Top