Yes I made a mistake, that's for dhcpcsvc6.dll is 6.1.7601.22648 (2956703) View attachment 32143 And it's 6.1.7601.22150 with 3004543, that's what I do not understand Thanks
That is, because the 2 patches contain the ominose file versions, too. The vendor may confuse with patches, because sometimes they package patches from scratch with some older files. On 98/2000/XP/2003 system that was not problem, because the installer always chooses files based on version (if available). Vista and newer systems use other method. When you install both patches (KB2956703 and KB3004543) together, the Windows Servicing Stack takes files into account from only one of the assembly (newer manifest or signing). So, if some files from the newer assembly are older than the other copy, the older file will by hardlinked and used instead of the newer. Unfortunately this may be a BUG or limitation of the Servicing Stack. Bigger problem is, that several updates contain the same, common assemblies (same name, identical or different versions, and some noncommons, that's why partially supersede). The Servicing Stack may handle badly such installations, as the files from all assemblies are hardlinked only from one update - the other may be totally ignored. The following model helps understanding the scenario: KB#1 contains: A1, B2, C1, D2, E1, F2 assemblies KB#2 contains: A2, B1, C2, D1, E2, F1 assemblies A1, B1, C1, D1, E1, F1 folders contain older files then A2, B2, C2, D2, E2, F2. So installing KB#1 and KB#2, the newer files from A2, B2, C2, D2, E2, F2 should be taken into life. However files from A1, B2, C1, D2, E1, F2 or A2, B1, C2, D1, E2, F1 will be active, depending on what patch is generally newer. So some of the older files will replace the newer ones. Some older patches are also affected by this problem, where each is only partially superseded by other. For example, if you install together: KB2973337 and KB2982706/KB2973351/KB2984972/KB2998097 and reboot, a lot of files will be older (04.12 instead of 05.30 from KB2973337), and probably function the of the patch KB2973337 will not be available. (Security Update KB2992611 contains updated files, so KB2973337 will function, but it doesn't need to by installed anymore, as it's fully superseded at file-by-file level. Checked with manually unpacking the patches. ) Another example: KB2894906 together KB2974617: ndismigplugin.dll is older version in the newer patch and installing KB2894906 will not ever restore the newer version.
Yes, but there should not install the 2 hotfixes but uninstall 2956703 and install 3004543 So the file, dhcpcsvc6.dll will be 6.1.7601.22150 (not 22648, because the 2956703 will be uninstalled)
2014/11/13: Spoiler Added: Code: 2912095 / AD_LDS 2990941-v3 3001232 3005781 / RDP Superseded Code: 2458125-v2 (by 2912095) / AD_LDS 2819485 (by 2990941-v3) 2957775 (by 2990941-v3) 2965351 (by 3001232) 2995635 (by 2912095) / AD_LDS 2998965 (by 3005781) / RDP
All the files (dhcpcore.dll, dhcpcsvc.dll, dhcpcore6.dll, dhcpcsvc6.dll, dhcpcmonitor.dll) are bundled under one sxs assembly and KB3004543 has the higher version for that assembly Code: amd64_microsoft-windows-dhcp-client-dll_31bf3856ad364e35_6.1.7601.22843_none_35e848d05e6647f0
Okay, because if I look at the "microsoft-windows-dhcp-client-dll" folder (2956703), the dhcpcsvc6.dll file is 22648 and with 3004543 is 21150 With 2956703 in System32 View attachment 32165 With 3004543 in System32 (2956703 uninstalled) View attachment 32166 That's why I did not understand For me, the 2956703 is not superseded, I think
You mean if you install both hotfixes, dhcpcsvc6.dll 22648 is found in system32? for me it's as expected, dhcpcsvc6.dll 21150 i can assure it's superseded, but you can suite yourself and keep it
Hello Murphy78, once again a question to your post 9554. When I try to integrate 2ND-Pass this updates are not integrated: KB2923545,KB2984981,KB2994023. DISM shows not the 100% mark. What's the matter? Thank's for help
Hi abbodi1406, Office 2013 lists have problems... I deleted all the listst from the folder and redownloaded them and still the problem exists. View attachment 32191 View attachment 32192
Yes that was my fault :S I had just started making major changes to the Office installer an as abbodi said, I got the compatibility for old/new WHD downloaders mixed up