From: PA Bear [MS MVP] on 13 Jun 2010 15:49 You don't need to keep reposting that Error. How did you determine that "Fix it 50123...is packaged with the updates from Windows Update site" (whatever that means)? What led you to believe that running Fix It 50123 manually might resolve the 0x643 errors? arnoldkrg wrote: > Hi PA Bear. > > I accessed http://support.microsoft.com/kb/971187 via IE7 Version > 7.0.5730.13. The Fix it did not run at all. So it couldnt Fix my Problem. > The Fix it 50123 WAS the problem because it is packaged with the updates > from the Windows Update site and NOT packaged with the updates from > http://www.microsoft.com/downloads/en/default.aspx It gave the same error > as > I originally asked about when trying to install from > http://support.microsoft.com/kb/971187: > > Event Type: Error > Event Source: MsiInstaller > Event Category: None > Event ID: 11720 > Date: 12/06/2010 > Time: 11:23:31 > User: xxxxxxxxx > Computer: xxxxxxxxxx > Description: > Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with > this > Windows Installer package. A script required for this install to complete > could not be run. Contact your support personnel or package vendor. > Custom > action RUN_32_PARSEARG script error -2146827859, Microsoft VBScript > runtime > error: ActiveX component can't create object: 'Scripting.FileSystemObject' > Line 22, Column 14, > > "PA Bear [MS MVP]" wrote: > >> Running the Fix It didn't resolve your problem or you wouldn't run the >> Fix >> It at all? >> >> Did you access http://support.microsoft.com/kb/971187 via IE (32-bit)? >> >> >> arnoldkrg wrote: >>> I have now managed to install all 3 of these updates. I refer you to the >>> posts by Wiesshund at: >>> >>> http://social.answers.microsoft.com/Forums/en/vistawu/thread/6e6faae4-83fc-4f8f-856d-5667dcb3143b >>> >>> I went to http://www.microsoft.com/downloads/en/default.aspx and >>> searched >>> for each of the problematic KB numbers and downloaded the standalone >>> updates >>> in turn. They each downloaded and installed succesfully so my PC is now >>> up >>> to date. >>> >>> The thing to note is that the standalone updates DO NOT contain Fix it >>> 50123 >>> packaged with them. Just the update executable. For example the download >>> for >>> KB979909 for my XP Pro machine is NDP20SP2-KB979909-x86.exe. >>> >>> But that still leaves me wondering why Fix it 50123 will not run on my >>> machine. >>> >>>> The three .NET updates fail to install. I have manually deleted all >>>> .Net >>>> Framework packages and reinstalled. I have applied Microsoft Fix It >>>> 50123. >>>> I have used the .NET cleanup tool to uninstall all .NET Framework >>>> packages >>>> twice and reinstalled in the correct order (3.5 first then 1.1 etc) and >>>> still I cannot get these updates to install. I opened a request for >>>> assistance via email and was simply referred back to here. >>>> >>>> I have the following in update history: >>>> >>>> Error Code: 0x643 >>>> Try to install the update again, or request help from one of the >>>> following >>>> resources. >>>> >>>> >>>> BUT the event log for each failed update is as follows: >>>> >>>> Event Type: Error >>>> Event Source: MsiInstaller >>>> Event Category: None >>>> Event ID: 11720 >>>> Date: 12/06/2010 >>>> Time: 11:23:31 >>>> User: xxxxxxxxx >>>> Computer: xxxxxxxxxx >>>> Description: >>>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with >>>> this >>>> Windows Installer package. A script required for this install to >>>> complete >>>> could not be run.... >> >> .
From: arnoldkrg on 13 Jun 2010 19:07 I followed information provided by you in the following post http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=c34b2289-ed19-47b6-aa64-46fbbd5dff4f&sloc=en-us Quote OPTION B: First run the Fix It in this KB article & see if the update will install after doing so: How to fix MSI software update registration corruption issues http://support.microsoft.com/kb/971187 Endquote The fact that Fix it 50123 is packaged with the updates is suggested, as I said in one of my earlier posts in this topic, in the following article: Quote I have further information which may be of help. I found this article via google: http://wmug.co.uk/blogs/peter/archive/2010/06/10/itmu-gets-into-bed-with-microsoft-fix-it.aspx endquote It is also reinforced by the error in the event log which clearly states that Fix it 50123 has failed to install (not that the update failed to install) The windows update site (whatever that means) can be found by clicking Tools in Internet explorer 7 and selecting Windows Update from the menu. This will take you to http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us where you can select high priority updates as well as optional updates. The problematic updates were found by this method, The Updates which actually worked and got rid of the yellow shield in my sys tray were found at http://www.microsoft.com/downloads/en/default.aspx The downloads there are clearly different from the ones at the Windows Update site (whatever that means) "PA Bear [MS MVP]" wrote: > You don't need to keep reposting that Error. > > How did you determine that "Fix it 50123...is packaged with the updates from > Windows Update site" (whatever that means)? > > What led you to believe that running Fix It 50123 manually might resolve the > 0x643 errors? > > > arnoldkrg wrote: > > Hi PA Bear. > > > > I accessed http://support.microsoft.com/kb/971187 via IE7 Version > > 7.0.5730.13. The Fix it did not run at all. So it couldnt Fix my Problem. > > The Fix it 50123 WAS the problem because it is packaged with the updates > > from the Windows Update site and NOT packaged with the updates from > > http://www.microsoft.com/downloads/en/default.aspx It gave the same error > > as > > I originally asked about when trying to install from > > http://support.microsoft.com/kb/971187: > > > > Event Type: Error > > Event Source: MsiInstaller > > Event Category: None > > Event ID: 11720 > > Date: 12/06/2010 > > Time: 11:23:31 > > User: xxxxxxxxx > > Computer: xxxxxxxxxx > > Description: > > Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with > > this > > Windows Installer package. A script required for this install to complete > > could not be run. Contact your support personnel or package vendor. > > Custom > > action RUN_32_PARSEARG script error -2146827859, Microsoft VBScript > > runtime > > error: ActiveX component can't create object: 'Scripting.FileSystemObject' > > Line 22, Column 14, > > > > "PA Bear [MS MVP]" wrote: > > > >> Running the Fix It didn't resolve your problem or you wouldn't run the > >> Fix > >> It at all? > >> > >> Did you access http://support.microsoft.com/kb/971187 via IE (32-bit)? > >> > >> > >> arnoldkrg wrote: > >>> I have now managed to install all 3 of these updates. I refer you to the > >>> posts by Wiesshund at: > >>> > >>> http://social.answers.microsoft.com/Forums/en/vistawu/thread/6e6faae4-83fc-4f8f-856d-5667dcb3143b > >>> > >>> I went to http://www.microsoft.com/downloads/en/default.aspx and > >>> searched > >>> for each of the problematic KB numbers and downloaded the standalone > >>> updates > >>> in turn. They each downloaded and installed succesfully so my PC is now > >>> up > >>> to date. > >>> > >>> The thing to note is that the standalone updates DO NOT contain Fix it > >>> 50123 > >>> packaged with them. Just the update executable. For example the download > >>> for > >>> KB979909 for my XP Pro machine is NDP20SP2-KB979909-x86.exe. > >>> > >>> But that still leaves me wondering why Fix it 50123 will not run on my > >>> machine. > >>> > >>>> The three .NET updates fail to install. I have manually deleted all > >>>> .Net > >>>> Framework packages and reinstalled. I have applied Microsoft Fix It > >>>> 50123. > >>>> I have used the .NET cleanup tool to uninstall all .NET Framework > >>>> packages > >>>> twice and reinstalled in the correct order (3.5 first then 1.1 etc) and > >>>> still I cannot get these updates to install. I opened a request for > >>>> assistance via email and was simply referred back to here. > >>>> > >>>> I have the following in update history: > >>>> > >>>> Error Code: 0x643 > >>>> Try to install the update again, or request help from one of the > >>>> following > >>>> resources. > >>>> > >>>> > >>>> BUT the event log for each failed update is as follows: > >>>> > >>>> Event Type: Error > >>>> Event Source: MsiInstaller > >>>> Event Category: None > >>>> Event ID: 11720 > >>>> Date: 12/06/2010 > >>>> Time: 11:23:31 > >>>> User: xxxxxxxxx > >>>> Computer: xxxxxxxxxx > >>>> Description: > >>>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with > >>>> this > >>>> Windows Installer package. A script required for this install to > >>>> complete > >>>> could not be run.... > >> > >> . > > . >
From: PA Bear [MS MVP] on 13 Jun 2010 19:14 That Fix It is NOT included in the installer you downloaded for manual install from the Download Center. If you couldn't even run the Fix It, you've probably got a hijackware infection on your hands. arnoldkrg wrote: > I followed information provided by you in the following post > > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=c34b2289-ed19-47b6-aa64-46fbbd5dff4f&sloc=en-us > > Quote > OPTION B: First run the Fix It in this KB article & see if the update will > install after doing so: > > How to fix MSI software update registration corruption issues > http://support.microsoft.com/kb/971187 Endquote > > The fact that Fix it 50123 is packaged with the updates is suggested, as I > said in one of my earlier posts in this topic, in the following article: > > Quote > I have further information which may be of help. I found this article via > google: > > http://wmug.co.uk/blogs/peter/archive/2010/06/10/itmu-gets-into-bed-with-microsoft-fix-it.aspx > endquote > > It is also reinforced by the error in the event log which clearly states > that Fix it 50123 has failed to install (not that the update failed to > install) > > The windows update site (whatever that means) can be found by clicking > Tools > in Internet explorer 7 and selecting Windows Update from the menu. This > will > take you to > http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us > where you can select high priority updates as well as optional updates. > The > problematic updates were found by this method, The Updates which actually > worked and got rid of the yellow shield in my sys tray were found at > http://www.microsoft.com/downloads/en/default.aspx The downloads there are > clearly different from the ones at the Windows Update site (whatever that > means) > > "PA Bear [MS MVP]" wrote: > >> You don't need to keep reposting that Error. >> >> How did you determine that "Fix it 50123...is packaged with the updates >> from Windows Update site" (whatever that means)? >> >> What led you to believe that running Fix It 50123 manually might resolve >> the 0x643 errors? >> >> >> arnoldkrg wrote: >>> Hi PA Bear. >>> >>> I accessed http://support.microsoft.com/kb/971187 via IE7 Version >>> 7.0.5730.13. The Fix it did not run at all. So it couldnt Fix my >>> Problem. >>> The Fix it 50123 WAS the problem because it is packaged with the updates >>> from the Windows Update site and NOT packaged with the updates from >>> http://www.microsoft.com/downloads/en/default.aspx It gave the same >>> error >>> as >>> I originally asked about when trying to install from >>> http://support.microsoft.com/kb/971187: >>> >>> Event Type: Error >>> Event Source: MsiInstaller >>> Event Category: None >>> Event ID: 11720 >>> Date: 12/06/2010 >>> Time: 11:23:31 >>> User: xxxxxxxxx >>> Computer: xxxxxxxxxx >>> Description: >>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with >>> this >>> Windows Installer package. A script required for this install to >>> complete >>> could not be run. Contact your support personnel or package vendor. >>> Custom >>> action RUN_32_PARSEARG script error -2146827859, Microsoft VBScript >>> runtime >>> error: ActiveX component can't create object: >>> 'Scripting.FileSystemObject' >>> Line 22, Column 14, >>> >>> "PA Bear [MS MVP]" wrote: >>> >>>> Running the Fix It didn't resolve your problem or you wouldn't run the >>>> Fix >>>> It at all? >>>> >>>> Did you access http://support.microsoft.com/kb/971187 via IE (32-bit)? >>>> >>>> >>>> arnoldkrg wrote: >>>>> I have now managed to install all 3 of these updates. I refer you to >>>>> the >>>>> posts by Wiesshund at: >>>>> >>>>> http://social.answers.microsoft.com/Forums/en/vistawu/thread/6e6faae4-83fc-4f8f-856d-5667dcb3143b >>>>> >>>>> I went to http://www.microsoft.com/downloads/en/default.aspx and >>>>> searched >>>>> for each of the problematic KB numbers and downloaded the standalone >>>>> updates >>>>> in turn. They each downloaded and installed succesfully so my PC is >>>>> now >>>>> up >>>>> to date. >>>>> >>>>> The thing to note is that the standalone updates DO NOT contain Fix it >>>>> 50123 >>>>> packaged with them. Just the update executable. For example the >>>>> download >>>>> for >>>>> KB979909 for my XP Pro machine is NDP20SP2-KB979909-x86.exe. >>>>> >>>>> But that still leaves me wondering why Fix it 50123 will not run on my >>>>> machine. >>>>> >>>>>> The three .NET updates fail to install. I have manually deleted all >>>>>> .Net >>>>>> Framework packages and reinstalled. I have applied Microsoft Fix It >>>>>> 50123. >>>>>> I have used the .NET cleanup tool to uninstall all .NET Framework >>>>>> packages >>>>>> twice and reinstalled in the correct order (3.5 first then 1.1 etc) >>>>>> and >>>>>> still I cannot get these updates to install. I opened a request for >>>>>> assistance via email and was simply referred back to here. >>>>>> >>>>>> I have the following in update history: >>>>>> >>>>>> Error Code: 0x643 >>>>>> Try to install the update again, or request help from one of the >>>>>> following >>>>>> resources. >>>>>> >>>>>> >>>>>> BUT the event log for each failed update is as follows: >>>>>> >>>>>> Event Type: Error >>>>>> Event Source: MsiInstaller >>>>>> Event Category: None >>>>>> Event ID: 11720 >>>>>> Date: 12/06/2010 >>>>>> Time: 11:23:31 >>>>>> User: xxxxxxxxx >>>>>> Computer: xxxxxxxxxx >>>>>> Description: >>>>>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem >>>>>> with >>>>>> this >>>>>> Windows Installer package. A script required for this install to >>>>>> complete >>>>>> could not be run.... >>>> >>>> . >> >> .
From: arnoldkrg on 14 Jun 2010 03:53 I wish you would actually read what I said. I have said already on several occasions that the updates available from the Download site do not contain the Fix it and so install with no problems. The same updates available via automatic updates DO contain the Fix it and so will NOT install for me and (it would seem ) for many others around the world. Oh and it wasnt me who found this way of fixing the problem it was someone else!!! As I also reported earlier!! I wont be answering to this topic anymore. It seems it is a waste of time talking to you or to anyone else connected with Microsoft!! BUT if someone else sees this Topic some of the information I provided may be of help to them. "PA Bear [MS MVP]" wrote: > That Fix It is NOT included in the installer you downloaded for manual > install from the Download Center. > > If you couldn't even run the Fix It, you've probably got a hijackware > infection on your hands. > > > arnoldkrg wrote: > > I followed information provided by you in the following post > > > > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=c34b2289-ed19-47b6-aa64-46fbbd5dff4f&sloc=en-us > > > > Quote > > OPTION B: First run the Fix It in this KB article & see if the update will > > install after doing so: > > > > How to fix MSI software update registration corruption issues > > http://support.microsoft.com/kb/971187 Endquote > > > > The fact that Fix it 50123 is packaged with the updates is suggested, as I > > said in one of my earlier posts in this topic, in the following article: > > > > Quote > > I have further information which may be of help. I found this article via > > google: > > > > http://wmug.co.uk/blogs/peter/archive/2010/06/10/itmu-gets-into-bed-with-microsoft-fix-it.aspx > > endquote > > > > It is also reinforced by the error in the event log which clearly states > > that Fix it 50123 has failed to install (not that the update failed to > > install) > > > > The windows update site (whatever that means) can be found by clicking > > Tools > > in Internet explorer 7 and selecting Windows Update from the menu. This > > will > > take you to > > http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us > > where you can select high priority updates as well as optional updates. > > The > > problematic updates were found by this method, The Updates which actually > > worked and got rid of the yellow shield in my sys tray were found at > > http://www.microsoft.com/downloads/en/default.aspx The downloads there are > > clearly different from the ones at the Windows Update site (whatever that > > means) > > > > "PA Bear [MS MVP]" wrote: > > > >> You don't need to keep reposting that Error. > >> > >> How did you determine that "Fix it 50123...is packaged with the updates > >> from Windows Update site" (whatever that means)? > >> > >> What led you to believe that running Fix It 50123 manually might resolve > >> the 0x643 errors? > >> > >> > >> arnoldkrg wrote: > >>> Hi PA Bear. > >>> > >>> I accessed http://support.microsoft.com/kb/971187 via IE7 Version > >>> 7.0.5730.13. The Fix it did not run at all. So it couldnt Fix my > >>> Problem. > >>> The Fix it 50123 WAS the problem because it is packaged with the updates > >>> from the Windows Update site and NOT packaged with the updates from > >>> http://www.microsoft.com/downloads/en/default.aspx It gave the same > >>> error > >>> as > >>> I originally asked about when trying to install from > >>> http://support.microsoft.com/kb/971187: > >>> > >>> Event Type: Error > >>> Event Source: MsiInstaller > >>> Event Category: None > >>> Event ID: 11720 > >>> Date: 12/06/2010 > >>> Time: 11:23:31 > >>> User: xxxxxxxxx > >>> Computer: xxxxxxxxxx > >>> Description: > >>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with > >>> this > >>> Windows Installer package. A script required for this install to > >>> complete > >>> could not be run. Contact your support personnel or package vendor. > >>> Custom > >>> action RUN_32_PARSEARG script error -2146827859, Microsoft VBScript > >>> runtime > >>> error: ActiveX component can't create object: > >>> 'Scripting.FileSystemObject' > >>> Line 22, Column 14, > >>> > >>> "PA Bear [MS MVP]" wrote: > >>> > >>>> Running the Fix It didn't resolve your problem or you wouldn't run the > >>>> Fix > >>>> It at all? > >>>> > >>>> Did you access http://support.microsoft.com/kb/971187 via IE (32-bit)? > >>>> > >>>> > >>>> arnoldkrg wrote: > >>>>> I have now managed to install all 3 of these updates. I refer you to > >>>>> the > >>>>> posts by Wiesshund at: > >>>>> > >>>>> http://social.answers.microsoft.com/Forums/en/vistawu/thread/6e6faae4-83fc-4f8f-856d-5667dcb3143b > >>>>> > >>>>> I went to http://www.microsoft.com/downloads/en/default.aspx and > >>>>> searched > >>>>> for each of the problematic KB numbers and downloaded the standalone > >>>>> updates > >>>>> in turn. They each downloaded and installed succesfully so my PC is > >>>>> now > >>>>> up > >>>>> to date. > >>>>> > >>>>> The thing to note is that the standalone updates DO NOT contain Fix it > >>>>> 50123 > >>>>> packaged with them. Just the update executable. For example the > >>>>> download > >>>>> for > >>>>> KB979909 for my XP Pro machine is NDP20SP2-KB979909-x86.exe. > >>>>> > >>>>> But that still leaves me wondering why Fix it 50123 will not run on my > >>>>> machine. > >>>>> > >>>>>> The three .NET updates fail to install. I have manually deleted all > >>>>>> .Net > >>>>>> Framework packages and reinstalled. I have applied Microsoft Fix It > >>>>>> 50123. > >>>>>> I have used the .NET cleanup tool to uninstall all .NET Framework > >>>>>> packages > >>>>>> twice and reinstalled in the correct order (3.5 first then 1.1 etc) > >>>>>> and > >>>>>> still I cannot get these updates to install. I opened a request for > >>>>>> assistance via email and was simply referred back to here. > >>>>>> > >>>>>> I have the following in update history: > >>>>>> > >>>>>> Error Code: 0x643 > >>>>>> Try to install the update again, or request help from one of the > >>>>>> following > >>>>>> resources. > >>>>>> > >>>>>> > >>>>>> BUT the event log for each failed update is as follows: > >>>>>> > >>>>>> Event Type: Error > >>>>>> Event Source: MsiInstaller > >>>>>> Event Category: None > >>>>>> Event ID: 11720 > >>>>>> Date: 12/06/2010 > >>>>>> Time: 11:23:31 > >>>>>> User: xxxxxxxxx > >>>>>> Computer: xxxxxxxxxx > >>>>>> Description: > >>>>>> Product: Microsoft Fix it 50123 -- Error 1720. There is a problem > >>>>>> with > >>>>>> this > >>>>>> Windows Installer package. A script required for this install to > >>>>>> complete > >>>>>> could not be run.... > >>>> > >>>> . > >> > >> . > > . >
From: arnoldkrg on 14 Jun 2010 08:38
One last post in the hope that it will help someone else I was finally able to run Fix it 50123 by doing the following: In windows ...start....run I entered the following: regsvr32 scrrun.dll Clicked OK I got the message that it was succesful. I next tried to run Fix it 50123 (after downloading to my desktop) and it installed successfully. "arnoldkrg" wrote: > The three .NET updates fail to install. I have manually deleted all .Net > Framework packages and reinstalled. I have applied Microsoft Fix It 50123. I > have used the .NET cleanup tool to uninstall all .NET Framework packages > twice and reinstalled in the correct order (3.5 first then 1.1 etc) and still > I cannot get these updates to install. I opened a request for assistance via > email and was simply referred back to here. > > I have the following in update history: > > Error Code: 0x643 > Try to install the update again, or request help from one of the following > resources. > > > BUT the event log for each failed update is as follows: > > Event Type: Error > Event Source: MsiInstaller > Event Category: None > Event ID: 11720 > Date: 12/06/2010 > Time: 11:23:31 > User: xxxxxxxxx > Computer: xxxxxxxxxx > Description: > Product: Microsoft Fix it 50123 -- Error 1720. There is a problem with this > Windows Installer package. A script required for this install to complete > could not be run. Contact your support personnel or package vendor. Custom > action RUN_32_PARSEARG script error -2146827859, Microsoft VBScript runtime > error: ActiveX component can't create object: 'Scripting.FileSystemObject' > Line 22, Column 14, > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 7b 39 32 41 43 35 46 35 {92AC5F5 > 0008: 39 2d 39 39 39 39 2d 34 9-9999-4 > 0010: 30 32 39 2d 39 43 31 45 029-9C1E > 0018: 2d 42 43 32 44 33 36 44 -BC2D36D > 0020: 30 46 45 46 30 7d 0FEF0} > > > Perhaps the event log may help someone help me to fix this problem. I have > been trying to fix this for days now. Ihave tried to run scripten.exe to > enable scripting but that says my software is newer and I dont need to run > it. I have also reinstalled the winows installer latest version (I believe) |