Update for Windows Vista for x64-based Systems (KB2541763)
Article ID: 2541763 - Last Review: June 29, 2011 - Revision: 2.0
A update that enables Internet Explorer in Windows XP, in Windows Vista, or in Windows Server 2008 to parse fragmented TLS/SSL handshake messages is available.
If you have had wireless connection problems since Wednesday, June the 30th onward, it might be fixed by uninstalling the above update.
The article (Article ID: 2541763) also mentions ways to edit your registry that may let the update work fault-free for me, but I don't know what it's breaking so why not just leave it the way it was, is my policy.
Article ID: 2541763 - Last Review: June 29, 2011 - Revision: 2.0
A update that enables Internet Explorer in Windows XP, in Windows Vista, or in Windows Server 2008 to parse fragmented TLS/SSL handshake messages is available.
Actually, after Windows Update installed this, Windows Vista 64-bit SP2 kept disconnecting the computer from my Netgear WNR1000v2 wireless router at random times. Uninstalling this update fixed the disconnect; fault-free so far and it's been 3 hours with multiple file download connections and streaming Flash and Java content across five Firefox tabs. No sweat.In certain situations, TLS/SSL handshake messages become too large to be contained in a single packet. In these situations, some third-party implementations of the TLS/SSL protocol fragment the messages before they are sent. However, the Microsoft implementation of the TLS/SSL protocol cannot parse fragmented messages. Therefore, Windows Internet Explorer on a computer that is running Windows XP, Windows Vista, or Windows Server 2008 cannot connect to servers that use a third-party TLS/SSL protocol. Additionally, you receive the following error message when you try to connect to such a server: "The page cannot be displayed."
If you have had wireless connection problems since Wednesday, June the 30th onward, it might be fixed by uninstalling the above update.
The article (Article ID: 2541763) also mentions ways to edit your registry that may let the update work fault-free for me, but I don't know what it's breaking so why not just leave it the way it was, is my policy.
My Computer
System One
-
- Manufacturer/Model
- Hewlett-Packard dv6936us
- CPU
- Intel Core 2 Duo "Merom" T5750, 2 GHz, stock clocking
- Motherboard
- stock Quanta 30D2, v.792E
- Memory
- 4 GHz, 667 MHz bus speed
- Graphics card(s)
- NVIDIA GeForce 8400M GS, stock
- Sound Card
- stock Realtek software-based
- Monitor(s) Displays
- stock 15.4" widescreen
- Screen Resolution
- stock 1280 X 800
- Hard Drives
- stock Toshiba MK2546GSX and a Western Digital 1TB MyBook
- PSU
- stock
- Case
- stock
- Cooling
- stock plus Rocketfish model RF-LAPCOL
- Mouse
- stock Synaptics Pointing Device
- Keyboard
- stock
- Internet Speed
- Ludicrous Speed (~10.9 Mbps, more or less)
- Other Info
- Browser: Namoroka v1.9.2.3666 64-bit build. Computer specs: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01485288&tmp_task=prodinfoCategory&lc=en&dlc=en&cc=us&product=3747246 I like chocolate milk!