Ah ok! but it seems you don't have to worry about that with the KB983234-V3, it updated msvbvm60.dll in syswow64 to the new version without having to mess around with access control. Its only used by Visual Basic 6.0 programs, I'm not sure what would happen if you have one of those open. It should ask for a restart if running the .msu directly in this case. If integrating the extracted cab with dism, it should still work. It looks like in your example you are talking about msvbvm60.dll being a file without a .msu file or a .cab in the correct format?
I was showing you the old way I updated it (the DLL without the installer,) thankfully dont need to do that anymore because there is a official MSU
I thought that may have been the case I wasn't sure about whether the older versions of the update had a .msu file or not. Still, since it is properly available now I guess it could be added?!
Ye if its MSU it will be added, however i also remebered before one of this VB updates wasnt msu so i didnt even bother
SoLoR you dont think this is a good hotfix to add? Its not really Japanese only Edit: its pretty hard to tell which font is newer, the default one in Windows 7 may just be newer (its bigger in size and has a higher version number)
I dont know... fact is it was made for Win7 in aug 2009. If they want this to apply for SP1 they can at least write it in to KB article, until then i dont want to add this OLD hotfix anywhere... also if SP1 font is actualy newer then i really dont see a point of using this.
If a Japanese Web site or application developed by old OS isn't used, it is not necessary to apply this Hotfix. The Japanese character set was changed from JIS90 to JIS2004 since Windows Vista. However, this change influenced a lot of system software in Japan. To have the software compatibility by a lot of guides in Japan, application of this Hotfix is recommended.
Thats true, but I don't think that applies to hotfixes that actually have a request button at the top (for the autorequest page). Also, this hotfix is too important, in reality, to be considered a hotfix instead of an update, let alone one that is only available by request. In regards to hotfixes available by order only, its unfortunate we don't have access to all the recent updates that fall into that category! I think a zukobonus like pre-sp1 would go down very nicely!
To create most up-to-date Windows 7 SP1 image, is it necessary to to slipstream both KB2484031 and KB2529073 into that image, or slipstream just KB2529073? Thanks for the tip.
Does anyone know of a good way to tell when a specific fix is superseded by another patch and what the KB number of the new patch would be? Example: According to the hotfix repository, KB2509553 has been removed, but I'm unable to easily tell with which fix it was replaced by. l am not currently integrating the complete update pack and only need to know which fix it was replaced by. Regular fixes are replaced quite often by other fixes and I was curious if there was an easy way to determine this. Thanks for any pointers..
Thanks for that, but is there the solution for this kind of problem in general? I don't want to keep bugging everyone each time I can't find what fix replaced the other. I tried Google, but with little success. Is there a list maintained somewhere that might contain this useful information? Thanks Edit: Other ones I'm having trouble finding: - KB2502285 replaced by ???????? - KB2484033 replaced by ???????? - KB2485376 replaced by KB2507618 (found this one)