Windows Installer Will Not Work

  • Thread starter Thread starter John in Florida
  • Start date Start date
J

John in Florida

Anytime I download a program and it uses Windows Installer it appears to be
going fine until just at the end and I get a message that says an unexpected
error occured, error code 2932. I've tried to reinstall Windows Installer,
which it says it was successful in doing, and tried to download the Windows
Installer Utility, but it uses Windows Installer to launch and I can't get
it. I've tried a system restore, without success, too. Any suggestions on
to correct this?
 
If you go to a command prompt and type "msiexec" without the quotes, and hit
enter, what happens?

(if you get a version number displayed, that may be good to quote, too.)
 
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
 
So--that's the installer, and it seems to be alive and well, and the major
version is current, although when I look at an SP3 machine the last two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI suffix
and the installer. This can be an indicator of virus or trojan activity,
but I could imagine it being caused by some other less worriesome kind of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


John in Florida said:
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.


Bill Sanderson said:
If you go to a command prompt and type "msiexec" without the quotes, and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote, too.)

message
 
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating! I
really do appreciate your time in trying to solve this. I've talked with a
certified Microsoft repairman and he ended up telling to use my restore disk
and start from scratch!

Bill Sanderson said:
So--that's the installer, and it seems to be alive and well, and the major
version is current, although when I look at an SP3 machine the last two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI suffix
and the installer. This can be an indicator of virus or trojan activity,
but I could imagine it being caused by some other less worriesome kind of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


John in Florida said:
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.


Bill Sanderson said:
If you go to a command prompt and type "msiexec" without the quotes, and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote, too.)

message
Anytime I download a program and it uses Windows Installer it appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Let's go over this again: Start from scratch.

(for later readers, please note this applies only to Windows XP--not Vista.)

1) uninstall Windows Defender, if it is now installed. If that fails, stop
there and write back.

2) download Windows Defender from scratch:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

Save the download to the desktop and double-click on it. What happens?

If that fails, with an error message, go to a command prompt. Navigate to
the desktop at the command prompt--if you need help with that let me
know--alternatively, copy the WindowsDefender.msi file to an easy to find
place like c:\ and go there.

try: msiexec /i windowsdefender.msi <enter>

what happens? Same error as in the previous step?

------------------------------------------------------

I'm trying to recall if you've been though this sequence:

http://support.microsoft.com/kb/886630/en-us

You should have the 3.1 install package handy first, I think--this is a
..exe, not a .MSI.

http://www.microsoft.com/downloads/...E776FD4138C&amp;displaylang=en&displaylang=en


John in Florida said:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating! I
really do appreciate your time in trying to solve this. I've talked with
a
certified Microsoft repairman and he ended up telling to use my restore
disk
and start from scratch!

Bill Sanderson said:
So--that's the installer, and it seems to be alive and well, and the
major
version is current, although when I look at an SP3 machine the last two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI
suffix
and the installer. This can be an indicator of virus or trojan activity,
but I could imagine it being caused by some other less worriesome kind of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote,
too.)

message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I
can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating! I
really do appreciate your time in trying to solve this. I've talked with a
certified Microsoft repairman and he ended up telling to use my restore disk
and start from scratch!

Bill Sanderson said:
So--that's the installer, and it seems to be alive and well, and the major
version is current, although when I look at an SP3 machine the last two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI suffix
and the installer. This can be an indicator of virus or trojan activity,
but I could imagine it being caused by some other less worriesome kind of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


John in Florida said:
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the quotes, and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote, too.)

message
Anytime I download a program and it uses Windows Installer it appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance that I'll
screw something up. I ran it, let Windows upload Service Pack 3, but still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean install,
ran it, with no problem. Tried to install Windows Live again, and once
again, at the end or the installation the familar Error Code 2932 appears and
rolls everything back.



Tom Emmelot said:
Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating! I
really do appreciate your time in trying to solve this. I've talked with a
certified Microsoft repairman and he ended up telling to use my restore disk
and start from scratch!

Bill Sanderson said:
So--that's the installer, and it seems to be alive and well, and the major
version is current, although when I look at an SP3 machine the last two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI suffix
and the installer. This can be an indicator of virus or trojan activity,
but I could imagine it being caused by some other less worriesome kind of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the quotes, and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote, too.)

message
Anytime I download a program and it uses Windows Installer it appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Let me see if I understand what you've said here:

You attempted to install Service Pack 3 for Windows XP, but that
installation ended with an Error 2932?

You were, however, able to uninstall and then reinstall Windows Defender,
without getting an error--both operations were successful?

However, what you really want to do is install Windows Live (can you give me
a URL so I'm sure I understand just what bits you are trying for)--and that
operation also fails with an error 2932, as the Service Pack install did.

My understanding of this error code is that it relates to being unable to
write a file to some specific location. The Service Pack install attempt
should have left a rather large log file which might contain more precise
information about what happened--See if you have "svcpack.log" in C:\Windows
(assuming Windows is installed in that location.)

You could either check through this file yourself to see if you can spot any
likely clues, or perhaps just cut and paste the tail end of the file to a
further message in this thread, if that looks relevant.
John in Florida said:
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance that
I'll
screw something up. I ran it, let Windows upload Service Pack 3, but
still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean
install,
ran it, with no problem. Tried to install Windows Live again, and once
again, at the end or the installation the familar Error Code 2932 appears
and
rolls everything back.



Tom Emmelot said:
Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating!
I
really do appreciate your time in trying to solve this. I've talked
with a
certified Microsoft repairman and he ended up telling to use my restore
disk
and start from scratch!

:

So--that's the installer, and it seems to be alive and well, and the
major
version is current, although when I look at an SP3 machine the last
two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want
to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI
suffix
and the installer. This can be an indicator of virus or trojan
activity,
but I could imagine it being caused by some other less worriesome kind
of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and
apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on
the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote,
too.)

message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I
can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Bill, I was able to install Service Pack 3 with no problem, uninstall Windows
Defender and reinstall it with no problem as well. The problem only occurs
when the program I'm installing uses Windows Installer. Yes, I'm trying to
install Windows Live Mail, the link I get it from is
http://get.live.com/wlmail/overview

I'm sorry, I don't know how to check to if I have svcpack.log installed or
what it says. Thanks so much for your help.

John

Bill Sanderson said:
Let me see if I understand what you've said here:

You attempted to install Service Pack 3 for Windows XP, but that
installation ended with an Error 2932?

You were, however, able to uninstall and then reinstall Windows Defender,
without getting an error--both operations were successful?

However, what you really want to do is install Windows Live (can you give me
a URL so I'm sure I understand just what bits you are trying for)--and that
operation also fails with an error 2932, as the Service Pack install did.

My understanding of this error code is that it relates to being unable to
write a file to some specific location. The Service Pack install attempt
should have left a rather large log file which might contain more precise
information about what happened--See if you have "svcpack.log" in C:\Windows
(assuming Windows is installed in that location.)

You could either check through this file yourself to see if you can spot any
likely clues, or perhaps just cut and paste the tail end of the file to a
further message in this thread, if that looks relevant.
John in Florida said:
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance that
I'll
screw something up. I ran it, let Windows upload Service Pack 3, but
still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean
install,
ran it, with no problem. Tried to install Windows Live again, and once
again, at the end or the installation the familar Error Code 2932 appears
and
rolls everything back.



Tom Emmelot said:
Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How frustrating!
I
really do appreciate your time in trying to solve this. I've talked
with a
certified Microsoft repairman and he ended up telling to use my restore
disk
and start from scratch!

:

So--that's the installer, and it seems to be alive and well, and the
major
version is current, although when I look at an SP3 machine the last
two
terms have higher numbers.

If you have a downloaded patch or application to install, and you want
to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the .MSI
suffix
and the installer. This can be an indicator of virus or trojan
activity,
but I could imagine it being caused by some other less worriesome kind
of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and
apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on
the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to quote,
too.)

message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download the
Windows
Installer Utility, but it uses Windows Installer to launch and I
can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
If the service pack installed fine, then there's no need to look at that
log.

Windows Defender uses the Windows Installer.

So--let's concentrate on Windows Live Mail.

I've installed this myself, but not on XP--so let me see check around and
see whether it creates a log file we can look at.

John in Florida said:
Bill, I was able to install Service Pack 3 with no problem, uninstall
Windows
Defender and reinstall it with no problem as well. The problem only
occurs
when the program I'm installing uses Windows Installer. Yes, I'm trying
to
install Windows Live Mail, the link I get it from is
http://get.live.com/wlmail/overview

I'm sorry, I don't know how to check to if I have svcpack.log installed or
what it says. Thanks so much for your help.

John

Bill Sanderson said:
Let me see if I understand what you've said here:

You attempted to install Service Pack 3 for Windows XP, but that
installation ended with an Error 2932?

You were, however, able to uninstall and then reinstall Windows Defender,
without getting an error--both operations were successful?

However, what you really want to do is install Windows Live (can you give
me
a URL so I'm sure I understand just what bits you are trying for)--and
that
operation also fails with an error 2932, as the Service Pack install did.

My understanding of this error code is that it relates to being unable to
write a file to some specific location. The Service Pack install attempt
should have left a rather large log file which might contain more precise
information about what happened--See if you have "svcpack.log" in
C:\Windows
(assuming Windows is installed in that location.)

You could either check through this file yourself to see if you can spot
any
likely clues, or perhaps just cut and paste the tail end of the file to a
further message in this thread, if that looks relevant.
message
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance that
I'll
screw something up. I ran it, let Windows upload Service Pack 3, but
still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean
install,
ran it, with no problem. Tried to install Windows Live again, and once
again, at the end or the installation the familar Error Code 2932
appears
and
rolls everything back.



:

Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How
frustrating!
I
really do appreciate your time in trying to solve this. I've talked
with a
certified Microsoft repairman and he ended up telling to use my
restore
disk
and start from scratch!

:

So--that's the installer, and it seems to be alive and well, and
the
major
version is current, although when I look at an SP3 machine the last
two
terms have higher numbers.

If you have a downloaded patch or application to install, and you
want
to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the
.MSI
suffix
and the installer. This can be an indicator of virus or trojan
activity,
but I could imagine it being caused by some other less worriesome
kind
of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download and
apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


in
message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation
on
the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the
quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to
quote,
too.)

in
message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says
an
unexpected
error occured, error code 2932. I've tried to reinstall Windows
Installer,
which it says it was successful in doing, and tried to download
the
Windows
Installer Utility, but it uses Windows Installer to launch and I
can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Here's what I'd recommend you do next to work towards resolving this:
Here are two Microsoft groups that specialize in the product you are having
trouble with:
microsoft.public.windows.live.mail.desktop
microsoft.public.windows.live.helpcommunity_platforum.feedback

I see you are posting via the Web-based forums, as opposed to NNTP, so let
me find URL's for those groups:

http://www.microsoft.com/communitie...dg=microsoft.public.windows.live.mail.desktop

Hmm - near as I can tell, that second group does not have an HTTP interface
to it.

If you post in the group above, let me know, and I'll see if I can follow it
there too.


Bill Sanderson said:
If the service pack installed fine, then there's no need to look at that
log.

Windows Defender uses the Windows Installer.

So--let's concentrate on Windows Live Mail.

I've installed this myself, but not on XP--so let me see check around and
see whether it creates a log file we can look at.

John in Florida said:
Bill, I was able to install Service Pack 3 with no problem, uninstall
Windows
Defender and reinstall it with no problem as well. The problem only
occurs
when the program I'm installing uses Windows Installer. Yes, I'm trying
to
install Windows Live Mail, the link I get it from is
http://get.live.com/wlmail/overview

I'm sorry, I don't know how to check to if I have svcpack.log installed
or
what it says. Thanks so much for your help.

John

Bill Sanderson said:
Let me see if I understand what you've said here:

You attempted to install Service Pack 3 for Windows XP, but that
installation ended with an Error 2932?

You were, however, able to uninstall and then reinstall Windows
Defender,
without getting an error--both operations were successful?

However, what you really want to do is install Windows Live (can you
give me
a URL so I'm sure I understand just what bits you are trying for)--and
that
operation also fails with an error 2932, as the Service Pack install
did.

My understanding of this error code is that it relates to being unable
to
write a file to some specific location. The Service Pack install
attempt
should have left a rather large log file which might contain more
precise
information about what happened--See if you have "svcpack.log" in
C:\Windows
(assuming Windows is installed in that location.)

You could either check through this file yourself to see if you can spot
any
likely clues, or perhaps just cut and paste the tail end of the file to
a
further message in this thread, if that looks relevant.
message
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance
that
I'll
screw something up. I ran it, let Windows upload Service Pack 3, but
still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean
install,
ran it, with no problem. Tried to install Windows Live again, and
once
again, at the end or the installation the familar Error Code 2932
appears
and
rolls everything back.



:

Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How
frustrating!
I
really do appreciate your time in trying to solve this. I've
talked
with a
certified Microsoft repairman and he ended up telling to use my
restore
disk
and start from scratch!

:

So--that's the installer, and it seems to be alive and well, and
the
major
version is current, although when I look at an SP3 machine the
last
two
terms have higher numbers.

If you have a downloaded patch or application to install, and you
want
to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the
.MSI
suffix
and the installer. This can be an indicator of virus or trojan
activity,
but I could imagine it being caused by some other less worriesome
kind
of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download
and
apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


in
message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation
on
the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the
quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to
quote,
too.)

"John in Florida" <[email protected]>
wrote in
message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says
an
unexpected
error occured, error code 2932. I've tried to reinstall
Windows
Installer,
which it says it was successful in doing, and tried to download
the
Windows
Installer Utility, but it uses Windows Installer to launch and
I
can't
get
it. I've tried a system restore, without success, too. Any
suggestions
on
to correct this?
 
Bill - Had a hard time getting back in here to post a reply then was out of
state and had no computer access. I'll post additional information on the
link you suggested.

Thanks



Bill Sanderson said:
Here's what I'd recommend you do next to work towards resolving this:
Here are two Microsoft groups that specialize in the product you are having
trouble with:
microsoft.public.windows.live.mail.desktop
microsoft.public.windows.live.helpcommunity_platforum.feedback

I see you are posting via the Web-based forums, as opposed to NNTP, so let
me find URL's for those groups:

http://www.microsoft.com/communitie...dg=microsoft.public.windows.live.mail.desktop

Hmm - near as I can tell, that second group does not have an HTTP interface
to it.

If you post in the group above, let me know, and I'll see if I can follow it
there too.


Bill Sanderson said:
If the service pack installed fine, then there's no need to look at that
log.

Windows Defender uses the Windows Installer.

So--let's concentrate on Windows Live Mail.

I've installed this myself, but not on XP--so let me see check around and
see whether it creates a log file we can look at.

John in Florida said:
Bill, I was able to install Service Pack 3 with no problem, uninstall
Windows
Defender and reinstall it with no problem as well. The problem only
occurs
when the program I'm installing uses Windows Installer. Yes, I'm trying
to
install Windows Live Mail, the link I get it from is
http://get.live.com/wlmail/overview

I'm sorry, I don't know how to check to if I have svcpack.log installed
or
what it says. Thanks so much for your help.

John

:

Let me see if I understand what you've said here:

You attempted to install Service Pack 3 for Windows XP, but that
installation ended with an Error 2932?

You were, however, able to uninstall and then reinstall Windows
Defender,
without getting an error--both operations were successful?

However, what you really want to do is install Windows Live (can you
give me
a URL so I'm sure I understand just what bits you are trying for)--and
that
operation also fails with an error 2932, as the Service Pack install
did.

My understanding of this error code is that it relates to being unable
to
write a file to some specific location. The Service Pack install
attempt
should have left a rather large log file which might contain more
precise
information about what happened--See if you have "svcpack.log" in
C:\Windows
(assuming Windows is installed in that location.)

You could either check through this file yourself to see if you can spot
any
likely clues, or perhaps just cut and paste the tail end of the file to
a
further message in this thread, if that looks relevant.
message
Ok, here's where I'm at. I did download the Dial-a-fix, because if a
software program can fix my error I feel there is less of a chance
that
I'll
screw something up. I ran it, let Windows upload Service Pack 3, but
still
get Error code 2932 at the end of program installation. I'm trying to
install Windows Live.

I then did as Bill suggested, removed Windows Defender, did a clean
install,
ran it, with no problem. Tried to install Windows Live again, and
once
again, at the end or the installation the familar Error Code 2932
appears
and
rolls everything back.



:

Hello there in Florida,

Here Tom from Amsterdam, ;)
Try this:
Download Dial-A-Fix,
http://wiki.djlizard.net/Dial-a-fix
Start it:
Click the green check mark and click Go.
After it has finished, try Windows Update and see if you can get your
updates installed.
I hope that post is helpful.

Regards >*< TOM >*<



John in Florida schreef:
I was so hopeful that this would work. It was the first creditable
suggestion I've received, and it made sense. However, I did as
instructed,
rebooted, but still get the dreaded Error 2932 code. How
frustrating!
I
really do appreciate your time in trying to solve this. I've
talked
with a
certified Microsoft repairman and he ended up telling to use my
restore
disk
and start from scratch!

:

So--that's the installer, and it seems to be alive and well, and
the
major
version is current, although when I look at an SP3 machine the
last
two
terms have higher numbers.

If you have a downloaded patch or application to install, and you
want
to
test, try doing:

msiexec /i xxx.msi

and see if that works.

My thought is that what is broken is the association between the
.MSI
suffix
and the installer. This can be an indicator of virus or trojan
activity,
but I could imagine it being caused by some other less worriesome
kind
of
bug.

At any rate, it isn't too hard to fix:

Go here:

http://www.dougknox.com/xp/file_assoc.htm

and read the instructions at the top of the page, then download
and
apply
according to those instructions, the MSI File Association Fix.

Let's see if that helps.


in
message
Bill,

This is what I get:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated
value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation
on
the
command line syntax.


:

If you go to a command prompt and type "msiexec" without the
quotes,
and
hit
enter, what happens?

(if you get a version number displayed, that may be good to
quote,
too.)

"John in Florida" <[email protected]>
wrote in
message
Anytime I download a program and it uses Windows Installer it
appears
to
be
going fine until just at the end and I get a message that says
an
unexpected
error occured, error code 2932. I've tried to reinstall
Windows
Installer,
which it says it was successful in doing, and tried to download
the
Windows
Installer Utility, but it uses Windows Installer to launch and
I
can't
 
Back
Top