/build/static/layout/Breadcrumb_cap_w.png

Windows Media Player 9.0 in Windows 2000 SP4

Recently Microsoft releases 2 security patches for Windows Media Player which out Security department in there infinite wisdom decided we should apply to out standard image. The patches are KB911564 and KB911565.

We are running Windows 2000 SP4 with just a standard install of Media Player. I created a package and tested the patched on a couple of machine in the lab. All went well. The package was then distributed to the general masses. Approximately half of the people appear to be fine and half now come up with an error message saying that the WMP.dll is the incorrect version. It has 9.0.0.3388 and is looking for 9.0.0.3008.

It was then decided that we would back out of this patch and ran the spuninst.bat file from the uninstall directory of that patch.

We are now in the position where people that may have been working after the original patch are not working now and some of the people that where not work still are not working.

I am now thinking about distributing a clean install of the Windows Media Player. I downloaded the EDP kit for Media player and have created a new package. I included the 2 patches into the package as well. The package runs but when it goes to install the patches the MSI displays an information screen with all of the switches for the patches and this requires the user to click ok. I am using the /qb! switch for the MSI

Does anyone have any suggestion or comments on how to proceed?

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ