I know this is redundant of me, but, of course none of your files are read only and I have run into something similar to this when the file is blocked and requires permission to run; ie: right click the file and hit properties. If there is an "unblock" button on the file properties page you hit unblock and apply your file will execute as expected. Just thought I would throw this out there in case it's something simple like that.
I've searched the forums and it seems KB983554 hasn't been mentioned. It's a very important update as you can see here (hehe, I can't post links... google it and maybe change this rule). I think it should be integrated in the next Solor's pack, if it isn't already in SP1 (I don't think so, since the storport.sys version is dated march 2011). Cheers.
I tried to install the KB2516405 (placerholders LDR) of 25/04/2011 but it is already installed (I already installed the KB2516405 of 17/04/2011) in fact, is what to replace that of 17.4.2011 by that of 25.4.2011 or what it is the same, and it was just to move to the folder LDR placerholders? thanks
im not trying to be an ass but Moved to LDR placeholders means exactly that... old update that was MOVED
SoLoR, please not to be an ass one more time but I need to ask this: So since you say moved 'old' update to LDR placeholders folder, what does this imply for our use of it? In a scenario where using automated integration to an image, do we not put those LDR placeholders in the list of updates, or do we? I really don't understand what it means. I always integrate the .msu's to my images from which I install in 1 go, but I'm not sure I should include those LDR ones or not. Thanks...
LDR placeholder update is update which sole purpose is to bump componenets in to LDR branch. So yes if you are integrating msu you kinda need them, if you are integrating update.mum/update-bf.mum then you dont need them.
so if I understand it, if we insert the Updates to ISO, and that does not update-bf.mum, LDR Updates (LDR placeholder) are integrated as a normal Updates? thanks
Thanks SoLoR and Ricktendo for the layman's explanation One particular question I could not find in the article: If I would name the LDR placeholder updates so that they get installed first (alphabetically, like put an "a" in front of their names), then for the sake of integration, is this the same as forcing LDR integration? Or, what happens if I integrate the LDR placeholder updates first, will the GDR ones still install, or? This is mainly what I'm trying to find out.
I dont think you have to, even if you install the LDR only hofix after you installed the GDR/LDR update, the latest LDR file from winsxs will be used (its just a guess) This leads me to believe this: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- No, there are LDR only updates in the main folder...LDR placeholder updates are separated because they have been superseded, but in order to passively force the install the LDR branch of the superseding hotfix they are not deleted If you use SoLoR's or bufardel's CMD install script you dont need them to (passively) force the install of LDR files
ok, I use no script so I use these LDR Updates I integrate the Updates with a special soft in ISO (the script of SoLoR should be used with dism or other, I think) so, I integrate the Updates present in "LDR placeholder" and all that in the x64 folder (in the repository) thank you for the explanation
KB971058 is not a update and KB2487335 has been superseded I found KB2506928-v2 to be aplicable, there may be others but I rather wait for SoLoR to sort thru and post them