L
Love Music
XPSP3,32bit, local install:
Ran MBSA 2.01 ok, clicked on "New Version Available", downloaded, tried open
Setup-x86-EN.msiMBSA, get: "... is not a valid windows installer pckg"...
Downloaded, tried open Win Installer 4.5 MSI WindowsXP-KB942288-v3-x86.exe
Get: ...is not a valid win32 applctn.
Executed:
F:\Documents and Settings\EDWARD\Desktop>
msiexec /i MBSASetup-x86-EN.msi /L*v MBSA.log
Get:
=== Verbose logging started: 11/26/2008 18:01:05 Build type: SHIP
UNICODE 3.01.4001.5512 Calling process:
F:\WINDOWS\system32\msiexec.exe ===
MSI (c) (04:00) [18:01:05:092]: Resetting cached policy values
MSI (c) (04:00) [18:01:05:092]: Machine policy value 'Debug' is 0
MSI (c) (04:00) [18:01:05:092]: ******* RunEngine:
******* Product: MBSASetup-x86-EN.msi
******* Action:
******* CommandLine: **********
MSI (c) (04:00) [18:01:05:092]: Note: 1: 2203 2: MBSASetup-x86-EN.msi
3: -2147287010
MSI (c) (04:00) [18:01:05:092]: MainEngineThread is returning 1620
=== Verbose logging stopped: 11/26/2008 18:01:05 ===
Any info in here ? Should I try to repair, replace or update msiexec ?
Ran MBSA 2.01 ok, clicked on "New Version Available", downloaded, tried open
Setup-x86-EN.msiMBSA, get: "... is not a valid windows installer pckg"...
Downloaded, tried open Win Installer 4.5 MSI WindowsXP-KB942288-v3-x86.exe
Get: ...is not a valid win32 applctn.
Executed:
F:\Documents and Settings\EDWARD\Desktop>
msiexec /i MBSASetup-x86-EN.msi /L*v MBSA.log
Get:
=== Verbose logging started: 11/26/2008 18:01:05 Build type: SHIP
UNICODE 3.01.4001.5512 Calling process:
F:\WINDOWS\system32\msiexec.exe ===
MSI (c) (04:00) [18:01:05:092]: Resetting cached policy values
MSI (c) (04:00) [18:01:05:092]: Machine policy value 'Debug' is 0
MSI (c) (04:00) [18:01:05:092]: ******* RunEngine:
******* Product: MBSASetup-x86-EN.msi
******* Action:
******* CommandLine: **********
MSI (c) (04:00) [18:01:05:092]: Note: 1: 2203 2: MBSASetup-x86-EN.msi
3: -2147287010
MSI (c) (04:00) [18:01:05:092]: MainEngineThread is returning 1620
=== Verbose logging stopped: 11/26/2008 18:01:05 ===
Any info in here ? Should I try to repair, replace or update msiexec ?