Btw remember you suggested to me that i would bring over %windir%\SoftwareDistribution\DataStore\DataStore.edb? Much to my suprise it worked.On a new install WU retained my settings for the things i had selected previously to hide. So no timeconsuming hiding needed on a new install.Just copied this file to the nessesary folder (needed to make the folder first) when the WIM was mounted.
well like you already figured it out, i made a mistake there is not other hotfix that would update system_windows_forms_dll thats why KB2518870 shouldnt be superseded...
Looks like SoLoR might have a few... updates to add to the repository on his next round! Update KB2615701 may be broken. The KB article says: Which is exactly what you see after installing this update! You cannot use safe mode, cannot use startup repair etc. I resorted to assuming that lsm.exe was the problem due to the message, and copying the previous lsm.exe over the top (whilst still using the newer kernel32.dll etc), upon which time it booted correctly. I tried uninstalling and reinstalling it again and the installation once again failed upon booting into Windows (where it auto-logs on). I ran sfc.exe on it, the claim is the file in the WinSxS folder (build 21824) does not have the hash its meant to and is corrupt, which makes sense. Just thought I'd warn people so they don't get caught, and also let SoLoR know for when he sorts all these new updates and possibly finds the same thing with the error.
Ya, around 50. I was almost worried something's wrong with kbupdate.info, since last month they kept adding already released hotfixes for Win7 SP1 and beta, lol.
SoLoR, just wondering on your next scan whether you can send me the complete list again? thought I'd update the superseded update uninstall list again. Thanks! - In case people are wondering, the updates in the repository don't represent all updates as there are often updates released with older files than existing updates. There are actually quite a few of these! Adding them to the superseded uninstall list means those that have installed some of these updates, either out of cycle, or are new to the repository, aren't left with numerous superseded, redundant files.
@burfadel have you any new info about 2615701 View attachment 11989 does the same error occur, if you integrate it in the install.wim and than make a clean install?
I don't know, I haven't tried! It could even be a certain circumstance thing too, or only affect LDR or GDR. I haven't tried any further with it, just thought I'd warn people about it since you need to use the 'repair computer' function and manually copy the ldm.exe back over since you can't use safe mode etc. Basically for me the update caused the very thing it was meant to fix. It could be that you try it and it works perfectly, or its only the LDR version thats stuffed and the GDR is fine... It terms of all the other files in the update, they are fine. In fact, I've still got the update installed just with the normal SP1 ldm.exe file and everything is working fine! I tried downloading the update again just in case, there definitely seems an issue there. If you're game try it out and see if you run into the same problem, keeping in mind to make a backup copy of ldm.exe (I copied it from the 'repair my computer' copy of Windows since its base is SP1. Anyways, make a copy, try it out (normal install, then LDR install), and if you run into any problems use the command prompt feature of 'repair my computer' (from pressing F8) to copy back the original file. It really shouldn't matter if its an existing copy or integrated. If I run sfc.exe it should copy the newer ldm.exe back over the current version I manually copied, but sfc.exe says the LDR version is corrupt in the WinSxS folder.