(imported topic written by ThomasVu)
When I run this fixlet the following error occurs: Download error: “Error processing completed download: Requested SHA1 60e1dcdda06d80b16aa69ea1524297f298c9e5c5 does not match actual SHA1 bba2e59a0f4ebb4bf961431f40d4f6c7ef4c706d”
Any ideas on how to solve this issue?
(imported comment written by JasonHonda)
This is an interesting situation. We are talking the download in Fixlet ID 295309501 in Patches for Windows (English) site. I manually downloaded the file myself and checked the sha1 and it does match the Fixlet,60e1…
Interestingly enough, the other Fixlet 295309503 does appear to have a download that was changed from when it was released. This is a somewhat normal occurrence. I’m filing a bug for the team to investigate and verify both Fixlets here. We should have things updated by tomorrow.
(imported comment written by jgstew)
This may be due to Microsoft updating their fix. The URL is this: http://download.microsoft.com/download/6/C/B/6CB85F36-7206-4B43-83BA-81496EF62FDB/MicrosoftFixit51010.msi
The change may be related to this issue: https://www.ibm.com/developerworks/community/forums/html/topic?id=b59717e2-ac44-4361-b3fd-8b349ef4a785
(imported comment written by sylviabeing)
The applicability of the patches have been updated by Microsoft also.
It was not applicable to Word 2013 in the original release while it is applicable to Word 2013 in current downloadable.
We are updating our content accordingly. Meanwhile, we are expecting re-release/revision confirmation from Microsoft.
Regards,
(imported comment written by jgstew)
UPDATED BELOW
These fixes as provided by IBM do not actually work. They take effect for the user that runs the fix only, so in this case the System account only. This means that it effectively fixes the problem for no one.
See the thread here about this:
https://www.ibm.com/developerworks/community/forums/html/topic?id=b59717e2-ac44-4361-b3fd-8b349ef4a785
I believe I have come up with a solution that uses local GPO to set the fix for all users.
Update:
The newest IBM fixlets do actually run the fix as the current user, which will solve the issue for a single user machine relatively well, but is still a problem for multi user machines. It would require an open action to eventually get the fix to all users. It will then require an open action to disable it to eventually remove the fix from all users.