From my experience with KB2615701, before installing the rest of the update I had issues, but once they were installed it works fine . I don't know which of the new update/updates make it work, just that you need to install all of them for it to work! This shouldn't be an issue . It should also be fine with integration since the rest of the updates would be integrated with it. I believe microsoft.grouppolicy.reporting.dll may be part of a component which is not normally installed. I have the file in the WinSxS folder only. Basically no harm having it installed or not.
Solved 2615701 issure after 2 hours of work I solved the problem with KB2615701 it should only be installed, if you install 2619234 first otherwise you get the View attachment 12040 error Note: for security reason install Windows6.1-KB2619234-x64.msu or Windows6.1-KB2619234-x86.msu and reboot your system before you install Windows6.1-KB2615701-x64.msu or Windows6.1-KB2615701-x86.msu otherwise, if the installation of 2619234 fails, you are back at the beginning/get the error again.
@burfadel maybe you can change the install script in a way, that 2615701 is only installed if 2619234 is installed before and the system is rebooted.
I do not agree with you, unfortunately. I installed KB2615701 first and had no problems at all. I really do not know what is going on. Maybe another one has an idea why different users have such problems...
It seems to be a possible issue and not a definitive one. Problem with changing the installer script is although its a good idea, its adding extra complexity to it. The script does check for the servicing stack update first, and installs it if available first, but its not along the same lines as update x must be installed before update y. Its quite possible Microsoft will release an updated update shortly, and that just makes things 'messier'.
KB2615701: is it only a problem when installing this update on a live system? I mostly integrate updates to the image only, so I'm wondering if this would be an issue at all in that scenario? If not I will simply leave this update out, because I think it would be better to have stability than the possibility of being locked out of a system?! Thanks for all the work on the updates, guys, it is appreciated.
I Recently integrated all the hotfix of solor's repository (including KB2615701) on my 64-bit Ultimate Image .... and it installs fine...
I agree w/ you. I have no issue w/ kb2615701 + latest hotfixes from Solor repository being integrated to my 64 bit image & testing it on vmware.
2615701 if somebody whats to reproduce the error try uninstalling 2619234 i made it on win7 x64 and got the same error again.
it's just the KB2615763-v2 that replaces KB2529073 and KB2528984? and KB2496290-v2 doesn't replace the KB2496290? (KB2496290 superseded?) thanks
KB2496290 deals with usbstor.sys, that is attached USB storage, and not the USB itself. It is a separate update KB2615763-v2 replaces KB2529073 and KB2528984. Don't bother looking up the kb article for KB2615763-v2, as it only shows the article for version 1 of the update, and the files updated and versions are incorrect! KB2615763-v2 updates all the actual USB driver files. KB2615763-v2: GDR: 6.1.7601.17701 LDR: 6.1.7601.21832 usbd.sys usbehci.sys usbohci.sys usbuhci.sys usbhub.sys usbport.sys usbccgp.sys KB2615763 (version 1, as listed in kb article) GDR: 6.1.7601.17586 LDR: 6.1.7601.21814 usbhub.sys usbccgp.sys
ok but I don't understand why KB2496290-v2 doesn't replace the KB2496290 KB2496290 usbstor.sys GDR (rtm): 6.1.7600.20881 LDR (sp1): 6.1.7601.21642 KB2496290-v2 usbstor.sys GDR (rtm): 6.1.7600.16877 LDR (rtm): 6.1.7600.21045 GDR (sp1): 6.1.7601.17684 LDR (sp1): 6.1.7601.21810 thanks
Do not install KB2496290 it can cause blue screen after connecting USB devices!! Apply only KB2496290-v2!