Thats right, if you don't integrate or also install the update.mum files WU will ask you. Try and installing the updates by double clicking on the .MSU files (for an update that contains both update.mum and update-bf.mum), you will find they will still ask to install if you use only update-bf.mum It does seem a bit pointless though, but unfortunately necessary.
Hmm, thats interesting! Maybe when integrating it works with just update-bf.mum, but online images require update.mum as well?... It would save a little space, wouldn't be too much though.
maybe... i will probably still install updates manualy with .msu, i was only doing this because when im doing fresh reinstall i want cleanest possible iso edit: so hm... i guess i can remove ORANGE updates from list on next update?
burfadel Thank you so much for your answer! I have additional questions to ask, if you do not mind. 1. Shouldn't Microsoft Visual C++ 2010 SP1 (x64) internally include Microsoft Visual C++ 2010 SP1 (x86)? Usually, 64-bit software includes 32-bit files within itself to be used. 2. Shouldn't Microsoft Visual C++ 2010 SP1 (x64) internally include files of Visual C++ 2005 and 2008? If both answers are no, it is definitely a hassle to install the most updated version of Microsoft Visual C++. I was always under the impression that installing Microsoft Visual C++ 2010 SP1 (x64) will include all previous version of Microsoft Visual C++ as well as 32 bit files, but I could be wrong. I really hope not. For expert users like you guys, you all can easily identify which LDR placeholders are. However, for a novice like me, labeling them as orange updates is necessary for me to know them. Still, the final decision lies on you, SoLoR, and I have to respect that.
The visual C++ 2005, 2008, and 2010 runtimes are related to the version of Visual C++ reflected in their names (2005, 2008, 2010). They are separate runtimes, and are onlty cumulative in ther own version in architecture. This basically means a SP1 runtime replaces the RTM ruintime, but nothing else. Since 2005, 2008, and 2010 runtimes are separate, you need to install all three. Also, since x64 programmes can't load x86 dll's, just like x86 programmes can't load x64 dll's, the runtimes are kept separate. So, on a x64 system, to keep up to date with the c++ runtimes you need to install all 6! the x86 and x64 versions of each of 2005, 2008, and 2010.
Mate if that so, would you be able to prepare some package with all most recent vc++ runtime installers? Besides for me it's a crap, that the lastest 2010 runtime doesn't contain previous packages...
Thing is, what method are you using for updating? Becasue if you are using burfadel script you dont need those orange updates at all, if you use that simple update.cmd you need them for now, but ill change that update.cmd as well...
SOLOR, maybe you could create a folder called LDR placeholder or similiar in your directory structure and put them in there.
SoLoR I did not use burfadel's script, because I use RT 7 Lite to integrate Windows updates and to slim down Windows. I will instruct RT 7 Lite to integrate the LDR placeholders first before other hotfixes, so that the resultant updates will be of LDR branch. I am just a novice and are reliant on such software to complete tasks. Anyway, SoLoR, it is best to follow the majority, as most of us here do not need to have LDR placeholders. My sole reason of wanting LDR placeholders to be labelled as orange is to facilitate in identifying them. Without this feature in the update list, it should be just a small problem for me. I have no complain about it, because the best interest for all is follow the majority. No worries, SoLoR. Cheers.
If you wanted to, you can use the script on an already installed system. It will identify those which are already installed, and will only install the LDR updates as required (it will still progress through the updates, but the updates already installed will pass reasonably quickly).
should be able to, don't just run it though! use: Code: call "VCRedist Installer.cmd" What that will do is run the installer, and when completed return to the other script. If you set it to just run, it will not return to the other script.