On review of the KB article, nothing jumps out at me. I would say that patch is not necessarily the place to look. Did you have an Office patch at/near the same time? I would think that is the more likely candidate for causing this.
Ridders brings up a very valid point. The file version for the working copy is shown as 6.3.9600.18460, whereas the not-working copy is 6.2.14393.1358 - which means, in more common speech, that version 6.3 works and 6.2 doesn't work for you. If for some reason you have an old version of Shell32 on the non-working system, you might very well have found your issue.
Unfortunately, it is not enough to just copy Shell32.DLL from the working machine to the non-working machine because the Windows registry gets involved here. In fact, it would be a VERY bad idea to attempt a simple copy. The odds are high that for an application extension (which is visible as one of the extended attributes), you would end up with a dangling registry link AND no current link to the updated file. You would need a registry fixer for the dangling link and I don't know what elements are needed to build a new registry link manually for the newer file. Let's just say that "ugly" doesn't come close to covering how bad that would be.
You might try to manually re-run an update to see if something catches the old version of Shell32.DLL and updates it. Otherwise, I am unsure where to go from here.
