Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > Updates download fine. None or Very Few install

Reply
Thread Tools Display Modes

Updates download fine. None or Very Few install

 
 
Prof Lombardo
Guest
Posts: n/a

 
      12-25-2007
I'm using a PC that has had no internet connection since I built it. I
recently moved it in to my study (I do a lot of chemical and protein modeling
so moving my higher spec unit seemed sensible). It went beserk when first
told to update...BUT all updates downloaded and installed fine. Since then,
and I can only assume this is due to an update download (windows installer
3.1, microsoft catalog etc) no microsoft updates will install. I have to
manually find the download and install it, but even then, some refuse stating
"The Setup.INI file is missing or incorrect". I'm almost certain this is due
to the new Windows Installer. Does anyone have similar problems, or better
still...A solution?

Many Thanks
Dr D Matthews
 
Reply With Quote
 
 
 
 
MowGreen [MVP]
Guest
Posts: n/a

 
      12-26-2007
Windows Version ?

Please post the last 50 or so lines of the WindowsUpdate.log
Start > Run > input

%windir%\windowsupdate.log

Click OK or press Enter
Copy and paste the last 50 or so lines into your reply.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Prof Lombardo wrote:
> I'm using a PC that has had no internet connection since I built it. I
> recently moved it in to my study (I do a lot of chemical and protein modeling
> so moving my higher spec unit seemed sensible). It went beserk when first
> told to update...BUT all updates downloaded and installed fine. Since then,
> and I can only assume this is due to an update download (windows installer
> 3.1, microsoft catalog etc) no microsoft updates will install. I have to
> manually find the download and install it, but even then, some refuse stating
> "The Setup.INI file is missing or incorrect". I'm almost certain this is due
> to the new Windows Installer. Does anyone have similar problems, or better
> still...A solution?
>
> Many Thanks
> Dr D Matthews

 
Reply With Quote
 
Prof Lombardo
Guest
Posts: n/a

 
      12-26-2007
Hi, Apologies - I'm running XP home

The lines are exceptionally repetative (sample below) and state that msi.dll
is the wrong version. I have located the library and determined it is in
fact version 3.0 rather than 3.1 which the log indicates is required. How do
I go about correcting this?

CUT
2007-12-26 18:35:26:406 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:26:406 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:26:406 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {F60C47C1-1386-4D9C-B153-E99CF0E217C5}.100, hr =
80241001
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {B78933CD-A405-4DEA-8D12-887C7D9A4B2F}.101, hr =
80241001
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
Installable rule, updateId = {B78933CD-A405-4DEA-8D12-887C7D9A4B2F}.101, hr =
80241001
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {8B9D10CE-E773-4355-A6DE-139181AE97EB}.101, hr =
80241001
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
Installable rule, updateId = {8B9D10CE-E773-4355-A6DE-139181AE97EB}.101, hr =
80241001
2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:671 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {D4BBFFD3-15CE-477A-B029-579F65B4563E}.101, hr =
80241001
2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:671 1600 14bc Agent WARNING: Failed to evaluate
Installable rule, updateId = {D4BBFFD3-15CE-477A-B029-579F65B4563E}.101, hr =
80241001
2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {A6034ADD-A29D-446E-A5A3-C7D1CA69F8F0}.101, hr =
80241001
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
Installable rule, updateId = {A6034ADD-A29D-446E-A5A3-C7D1CA69F8F0}.101, hr =
80241001
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {A4AFA9F3-9EF7-4737-A3A4-2C939CBC4437}.101, hr =
80241001
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
Installable rule, updateId = {A4AFA9F3-9EF7-4737-A3A4-2C939CBC4437}.101, hr =
80241001
2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:28:109 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:28:109 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {D72155F3-8AA8-4BF7-9972-0A696875B74E}.100, hr =
80241001
2007-12-26 18:35:28:468 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
Version 3.1 is required.
2007-12-26 18:35:28:468 1600 14bc Agent WARNING: Failed to evaluate
Installed rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr =
80241001
2007-12-26 18:36:24:796 1600 14bc Driver DriverUtil marking
{7353F529-8808-4FFC-8887-33B1080E042B}.100 e_detectionStateInstallable
2007-12-26 18:36:24:796 1600 14bc Driver Matched driver to device
PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01
2007-12-26 18:36:24:796 1600 14bc Driver Status: 0x180200a, ProblemNumber:
00000000
2007-12-26 18:36:24:796 1600 14bc Driver Calculated driver attributes as
0x00000000
2007-12-26 18:36:24:796 1600 14bc Driver DriverUtil marking
{A2FA6038-D71E-4CE8-9884-8A57C7C3235F}.100 e_detectionStateInstallable
2007-12-26 18:36:24:796 1600 14bc Driver Matched driver to device
Monitor\PHL0839
2007-12-26 18:36:24:796 1600 14bc Driver Status: 0x180600a, ProblemNumber:
00000000
2007-12-26 18:36:24:796 1600 14bc Driver Calculated driver attributes as
0x00000000


I'm fairly sure I know what the last portion is about, as I have manually
updated these drivers from the manufacturer. The remainder of the the log
simply repeats MSI.dll is version 3.0, should be 3.1

Help would be greatly appreciated

Matt.
"MowGreen [MVP]" wrote:

> Windows Version ?
>
> Please post the last 50 or so lines of the WindowsUpdate.log
> Start > Run > input
>
> %windir%\windowsupdate.log
>
> Click OK or press Enter
> Copy and paste the last 50 or so lines into your reply.
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> Prof Lombardo wrote:
> > I'm using a PC that has had no internet connection since I built it. I
> > recently moved it in to my study (I do a lot of chemical and protein modeling
> > so moving my higher spec unit seemed sensible). It went beserk when first
> > told to update...BUT all updates downloaded and installed fine. Since then,
> > and I can only assume this is due to an update download (windows installer
> > 3.1, microsoft catalog etc) no microsoft updates will install. I have to
> > manually find the download and install it, but even then, some refuse stating
> > "The Setup.INI file is missing or incorrect". I'm almost certain this is due
> > to the new Windows Installer. Does anyone have similar problems, or better
> > still...A solution?
> >
> > Many Thanks
> > Dr D Matthews

>

 
Reply With Quote
 
MowGreen [MVP]
Guest
Posts: n/a

 
      12-26-2007
Only updates that were meant to be installed with the previous version
of Windows Installer have installed.
What you're seeing is a 'mixed version soup' of .dlls associated with
Windows Installer or, the Version level is 'stuck'.

The culprit *may* be security software that is preventing the
updating/replacing of said .dlls or the executable itself.

0x80241001 WU_E_MSI_WRONG_VERSION
MSI patching is disabled by policy
The MSI version on the machine is less than what we expect

Suggest you download Windows Installer 3.1 (v.2) and save it:
http://www.microsoft.com/downloads/d...DisplayLang=en

Unregister Windows Installer and remove it's associated files:
http://support.microsoft.com/kb/886630

There are instructions to restart in Safe Mode if removing the files can
not be done in normal Windows mode.
Stopping the Windows Installer service via the services console *should*
suffice if you find the service has started because it is set to run at
system startup.

* Be sure to check in system32\dllcache for backup copies of the files
described in KB886630 and delete these, too *

Once all files associated with WI are gone, set the Windows Installer
service to Manual via the services console and then install Windows
Installer 3.1 (v.2)
Reboot after doing so
If there is still an issue installing it, there will now be a
KB893803v2.log located in %windir% that should provide a clue as to why
the installation is failing.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



Prof Lombardo wrote:

> Hi, Apologies - I'm running XP home
>
> The lines are exceptionally repetative (sample below) and state that msi.dll
> is the wrong version. I have located the library and determined it is in
> fact version 3.0 rather than 3.1 which the log indicates is required. How do
> I go about correcting this?
>
> CUT
> 2007-12-26 18:35:26:406 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:26:406 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:26:406 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {F60C47C1-1386-4D9C-B153-E99CF0E217C5}.100, hr =
> 80241001
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {B78933CD-A405-4DEA-8D12-887C7D9A4B2F}.101, hr =
> 80241001
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
> Installable rule, updateId = {B78933CD-A405-4DEA-8D12-887C7D9A4B2F}.101, hr =
> 80241001
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {8B9D10CE-E773-4355-A6DE-139181AE97EB}.101, hr =
> 80241001
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:546 1600 14bc Agent WARNING: Failed to evaluate
> Installable rule, updateId = {8B9D10CE-E773-4355-A6DE-139181AE97EB}.101, hr =
> 80241001
> 2007-12-26 18:35:27:546 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:671 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {D4BBFFD3-15CE-477A-B029-579F65B4563E}.101, hr =
> 80241001
> 2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:671 1600 14bc Agent WARNING: Failed to evaluate
> Installable rule, updateId = {D4BBFFD3-15CE-477A-B029-579F65B4563E}.101, hr =
> 80241001
> 2007-12-26 18:35:27:671 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {A6034ADD-A29D-446E-A5A3-C7D1CA69F8F0}.101, hr =
> 80241001
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
> Installable rule, updateId = {A6034ADD-A29D-446E-A5A3-C7D1CA69F8F0}.101, hr =
> 80241001
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {A4AFA9F3-9EF7-4737-A3A4-2C939CBC4437}.101, hr =
> 80241001
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:27:875 1600 14bc Agent WARNING: Failed to evaluate
> Installable rule, updateId = {A4AFA9F3-9EF7-4737-A3A4-2C939CBC4437}.101, hr =
> 80241001
> 2007-12-26 18:35:27:875 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:28:109 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:28:109 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {D72155F3-8AA8-4BF7-9972-0A696875B74E}.100, hr =
> 80241001
> 2007-12-26 18:35:28:468 1600 14bc EEHndlr FATAL: MSI DLL version is 3.0.
> Version 3.1 is required.
> 2007-12-26 18:35:28:468 1600 14bc Agent WARNING: Failed to evaluate
> Installed rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr =
> 80241001
> 2007-12-26 18:36:24:796 1600 14bc Driver DriverUtil marking
> {7353F529-8808-4FFC-8887-33B1080E042B}.100 e_detectionStateInstallable
> 2007-12-26 18:36:24:796 1600 14bc Driver Matched driver to device
> PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01
> 2007-12-26 18:36:24:796 1600 14bc Driver Status: 0x180200a, ProblemNumber:
> 00000000
> 2007-12-26 18:36:24:796 1600 14bc Driver Calculated driver attributes as
> 0x00000000
> 2007-12-26 18:36:24:796 1600 14bc Driver DriverUtil marking
> {A2FA6038-D71E-4CE8-9884-8A57C7C3235F}.100 e_detectionStateInstallable
> 2007-12-26 18:36:24:796 1600 14bc Driver Matched driver to device
> Monitor\PHL0839
> 2007-12-26 18:36:24:796 1600 14bc Driver Status: 0x180600a, ProblemNumber:
> 00000000
> 2007-12-26 18:36:24:796 1600 14bc Driver Calculated driver attributes as
> 0x00000000
>
>
> I'm fairly sure I know what the last portion is about, as I have manually
> updated these drivers from the manufacturer. The remainder of the the log
> simply repeats MSI.dll is version 3.0, should be 3.1
>
> Help would be greatly appreciated
>
> Matt.
> "MowGreen [MVP]" wrote:
>
>
>>Windows Version ?
>>
>>Please post the last 50 or so lines of the WindowsUpdate.log
>>Start > Run > input
>>
>>%windir%\windowsupdate.log
>>
>>Click OK or press Enter
>>Copy and paste the last 50 or so lines into your reply.
>>
>>
>>MowGreen [MVP 2003-2008]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>Prof Lombardo wrote:
>>
>>>I'm using a PC that has had no internet connection since I built it. I
>>>recently moved it in to my study (I do a lot of chemical and protein modeling
>>>so moving my higher spec unit seemed sensible). It went beserk when first
>>>told to update...BUT all updates downloaded and installed fine. Since then,
>>>and I can only assume this is due to an update download (windows installer
>>>3.1, microsoft catalog etc) no microsoft updates will install. I have to
>>>manually find the download and install it, but even then, some refuse stating
>>>"The Setup.INI file is missing or incorrect". I'm almost certain this is due
>>>to the new Windows Installer. Does anyone have similar problems, or better
>>>still...A solution?
>>>
>>>Many Thanks
>>>Dr D Matthews

>>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
E-mails download fine then disappear Coccinelle Windows Vista Mail 4 09-11-2008 05:00 AM
updates download fine, but 5 day delay in installing Glenn Dardick Windows Update 1 09-14-2006 05:11 PM
Updates don't install after download using, semi-Automatic Updates don Windows Update 2 05-17-2006 09:50 PM
Windows update download freezing - (internet connection fine) David Windows Update 0 10-16-2004 05:35 PM
Scans fine but cannot find page to download. Dale Windows Update 0 10-03-2003 10:17 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59