HP Mobile Thin Client Microsoft Critical Updates 2.1.142 for XP Download

Posted at December 23, 2024 by PCI-DB Team

Install Driver Automatically

Device Name	HP Mobile Thin Client Microsoft Critical Updates 2.1.142 for XP
Category	Other Drivers Tools
Manufacturer	MICROSOFT
File Size	10.2 MB
Supported OS	Windows XP

HP Mobile Thin Client Microsoft Critical Updates 2.1.142 for XP Description

This package provides all the Micrososft Security Updates that are needed for
the following Mobile Thin Client XPe Images:

HP 4410t Mobile Thin Client Microsoft Windows XP Embedded (XPe) Image 2.1.142

PRODUCT TYPE(S): 
Notebooks

PRODUCT MODEL(S): 
HP 4410t Mobile Thin Client

ENHANCEMENTS: 
This package includes all the QFEs from previous versions, and adds the
following new QFEs (listed by month).

September 2009 QFEs:

- Microsoft QFE MS09-045 (KB971961) - For more information, see Microsoft
Knowledge Base Article 971961, "Vulnerability in JScript Scripting Engine
Could Allow Remote Code Execution."

- Microsoft QFE MS09-047 (KB973812) - For more information, see Microsoft
Knowledge Base Article 968816, "Vulnerabilities in Windows Media Format
Could Allow Remote Code Execution."  NOTE:  This QFE replaces
Microsoft QFE MS06-078 (KB923689).
PREREQUISITES: 
- This add-on requires uncompressed free space on the flash memory (Drive C:)
and uncompressed free space in the temporary folder. These space requirements
must be met in order to successfully deploy this add-on.

* Space required on the flash memory for installation: 30 MB
* Space required on the flash memory after installation: 25 MB (with NTFS
Compression)
* Space required in the temporary folder for installation: Depends on
individual QFE being installed

If there is not enough space on the RAM Disk (Z:), it may be necessary to
increase the RAM Disk up to its maximum size to deploy the add-on. After
installation, HP recommends that the RAM drive be set back to its original size.

NOTE

: Before increasing or decreasing the size of the RAM Disk, reboot the
machine so that unwanted changes do not get committed to the flash memory.

If there is still not enough space on the RAM Disk to deploy the add-on, HP
recommends that the system %TEMP% and %TMP% variables be temporarily re-defined
to either the (C:) drive or a network share on the deployment server, and that
the setup program be executed from the deployment server.

HOW TO USE: 
Follow the steps that match your environment, Managed Solution or Non-Managed
Solution.

Use the following steps for a Managed Solution:

1. Download the file by clicking the "Download" or "Obtain Software" button and
saving the file to a folder on your hard drive (make a note of the folder where
the downloaded file is saved).
2. Double-click the downloaded file and follow the on-screen instructions to
unpack the individual QFE SoftPaq files to a designated location.
3. Double-click the individual QFE SoftPaqs and follow the on-screen
instructions to unpack the specific QFE files to a designated location.
4. Incorporate the individual QFE executables into your management environment
and deploy the solution to all HP Thin Clients.
5. Commit the changes to the Thin Client (requires Administrative privileges).
6. Restart the Thin Client.
Use the following steps for a Non-Managed Solution:

1. Download the file by clicking the "Download" or "Obtain Software" button and
saving the file to a folder on your hard drive (make a note of the folder where
the downloaded file is saved).
2. Double-click the downloaded file (SP#####.EXE) and follow the on-screen
instructions to unpack the contents to a designated location.
3. Double-click the individual QFE SoftPaqs and follow the on-screen
instructions to unpack the specific QFE files to a designated location.
4. Execute the individual QFE executables on the respective HP Thin Client via
CD-ROM, DOK, Network Share, etc.
5. Commit the changes to the Thin Client (requires Administrative privileges).
6. Restart the Thin Client.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related MICROSOFT Drivers