The April 2009 Windows XP Embedded and Windows Embedded Standard Security Updates - Product Download is now available on the ECE for Windows® Embedded Standard 2009 and/or Microsoft® Windows® XP Embedded with Service Pack 2, Feature Pack 2007, Update Rollup 1.0 and Service Pack 3. These are the DQI updates that can be applied directly to runtimes that include the dependencies necessary to handle the WinSE installer.
This download is a cumulative update which incorporates all updates from prior months. Therefore you do not need to download and install previous monthly updates.
The Updates in this rollup package are arranged in the following way:
The April Security updates include:
For full details on the April 2009 Embedded Windows Security Updates see the ECE site:
If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
PingBack from http://asp-net-hosting.simplynetdev.com/april-2009-security-updates-are-now-available-on-the-ece/
I wonder if WRITE.EXE and WRITE.HLP from WFW3.11 are vulnerable.
I put them on my system (in C:\WINDOWS) and pointed *.WRI files to open using Write. It seems to work fine on XP Pro.
If the text converters are the problem I'd think WFW 311 WRITE.EXE will be OK.(Win9x Write uses the converters)
MSO Word 2007 gives a nice scary warning now when opening *.WRI files and I don't want to install Word Viewer on top of a full MSO installation.
Are you doing this on an XP Embedded or Windows Embedded Standard 2009 system? Office products like Word are not licensed for use on Embedded.
I posted here in the wrong place. I am not dealing with an embedded system, just a normal XP Pro install.
I did a custom (re)install. As a courtesy I usually look at older programs (espesially 16 bit) if I have time after a service pack release before releasing a computer I install. I noticed the "read me" file did not work for one of these program, then fished around and found it was due to the cumulative security update.
I put the WFW 3.1 Write on the system, and searched MSDN blogs for KB960477. This KB didn't get a lot of notice, I think 3 hits total. I was intending to fish and see if I defeated the purpose of the update, or if I'm OK here.