I’ve been going crazy trying to fix a problem with uploading a file over a https secured ftp site for one of my uses. I contacted their help desk and it looks like KB2585542 broke a few things. I removed names and URLs on the rest of the post.

Per our conversation: Recent Microsoft patches (Microsoft KB2585542) on windows 7 has broken the IE upload facility for our secureftp environment. On Microsoft TechNet, many users are discussing their respective websites broken. Please notice the URL: also, they say that Microsoft FixIt patch available for people that are having trouble following this update. The patch is available in KB2643584: Observations: 1) Firefox, all versions work just fine. 2) This problem does not exist on windows XP with IE8 etc because the update seems to be on Windows 7 only. 3) All client software continue to work fine on all other secureftp supported protocols ( SFTP, FTP over SSL, HTTPS using ST Client) Please refer to the attachment for user workaround information.

The attachment goes as follows:

Solution to HTTP 500 ERROR or BLANK page on file uploads to servers using IE on WINDOWS7 etc. Problem: Microsoft KB2585542 fixes a security issue with the CBC SSL ciphers in could cause the following issues with Internet Explorer: - Internal Server Error (HTTP error 500) while trying to upload files using the Web Client UI - Blank page while trying to upload files using the Web Client UI - Unable to perform certain operations in the Admin UI. This includes export and generate certificates, update user account settings, etc. Solution: In order to resolve this you could use one of the following workarounds: 1. Client workaround: - Go Internet Option Advanced and uncheck TLS 1.0. The ST Web Client UI would work as expected using only SSL 3.0. 2. Client workaround: - Run regedit and navigate to the following key: HKEYLOCALMACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNEL - Add 32bit DWORD registry value SendExtraRecord = 2. 3. Client workaround: - Access the Web Client UI using another browser that does not use the Windows Internet Options such as Mozilla Firefox. (and not Google Chrome) 4. Client workaround: - Uninstall the KB2585542 update and disable it in WSUS.