In the Microsoft KB article (http://support.microsoft.com/?kbid=2835361) it does actually show the following file requirements for Windows 7 & 2008 R2:
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name File version File size Date Time Platform Dwrite.dll 6.1.7601.18126 1,545,728 10-Apr-2013 05:45 x64 Dwrite.dll 6.1.7601.22296 1,545,728 10-Apr-2013 05:21 x64 Dwrite.dll 6.2.9200.16571 1,643,520 02-Apr-2013 22:51 x64 Dwrite.dll 6.2.9200.20675 1,643,520 10-Apr-2013 05:21 x64 Dwrite.dll 6.1.7601.18126 1,077,760 10-Apr-2013 05:02 x86 Dwrite.dll 6.1.7601.22296 1,077,760 10-Apr-2013 05:14 x86 Dwrite.dll 6.2.9200.16571 1,247,744 09-Apr-2013 23:34 x86 Dwrite.dll 6.2.9200.20675 1,247,744 10-Apr-2013 05:15 x86
Are you experiencing any installation failure or trouble when deploying this patch?
thanks for your answer. Yes, re-installation fails ("Security Update is already installed on this computer") . I've seen these file information too, but it must be erroneous. I cannot help, but the first two digits represent major version.minor version. Hence 6.1 is attributed to Windows 7/Server 2008, and 6.2 to Windows 8/Server 2012. Microsoft will confirm this fact as does its MBSA which does in my case not show KB2835361 as missing.
I hope you can get confirmation as well as an explanation for the "6.2." version files under Windows 7 & Server 2012 directly from Microsoft Support.
If it is indeed detecting as missing and failing installation it would be best if we could have you open a case directly with support. It appears to me that you could be running into a detection issue concerning the file branch.
If you could please run through the steps for Protect console logging as described in the below linked document it would greatly help us in getting this fixed.
sorry, but I can't assist you in solving the problem. Youc can find a detailed log posted by angkgupta, filed under "Problem with MS13-054" in July 31 2013 here: http://community.shavlik.com/message/2245401#2245401.
Please unterstand, that I have not the resources to reverse engineer the problem.