Hi there,
Im looking to deploy an XP Update (KB....) to some users via Group Policy.
In order to do so I need to repackage the update (exe format) into an msi format.
I take a snapshot and I end up with my MSI as planned.
But as expected, when I run the MSI locally as an administrator, due to WFP i get
an error saying "Error 1931.The Windows Installer service cannot update the system file C:\WINDOWS\system32\drivers\http.sys because the file is protected by Windows".
Im just wondering if there is a potential work around?
Would it be feasible to rename the file via a script so that the msi can write the
newer version of the above file to the mentioned directory?
Although I doubt this would work.
Many thanks for any input.
Kind regards
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Repackaging application should always be your last resort. And repackaging KB is very bad.

I would suggest using WinSUS to deploy any KB or patches from Microsoft.
Answered 02/12/2007 by: wd40
Orange Senior Belt

Please log in to comment
Yes, you can't repackage a windows patch.

You could make an MSI wrapper for it I suspect. Just add the update as a file in your MSI then call it with a custom action.
Answered 02/13/2007 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Ok, many thanks for the info guys.
Ill give the custom action a bash and see how I go.
As always, thank you for your help
and best regards.
Answered 02/15/2007 by: shamrock
Orange Belt

Please log in to comment
Hi shamrock,
maybe, you give WIWW a try first. Get it from here: http://n.ethz.ch/student/heim/msi/WIWW_0-0-0-1.zip
Regards, Nick
Answered 02/15/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity