Yes, that's what SoLoR's "Update.cmd" script does. It's in the repo with the other files and in the "KB000000" .7z file. BTW, @SoLoR: there is a problem with downloading the update.cmd file in the repo. It says "404 - File or directory not found." Yes, 7601.21831 is the current version for x64 (you have the good version).
I was actually wondering if it you could make one more option... I realize everyone here probably always wants the very latest LDR branch. But I'd also like the option to JUST have only the GDR updates. I realize a lot of untested bugfixes wouldn't be installed but a system with all GDR updates would be very secure. I've read a few cases where once someone is on the LDR update branch, various components didn't work right but staying with all GDR at least until the service pack is sometimes safer. It also may be good for testing. Have options for 1. All possible LDR (EDIT: LDR or GDR if LDR not present) and another option for 2. Just all the GDR updates or 3. Both GDR+LDR, would also cover all possible bases. Well, its just an idea of how to make your script very universal... Happy Holiday burfadel!
Thank you for the detailed response. You explained it very well. It makes sense that most of the hotfixes would have an LDR component. I assume that if a hotfix is bad for some reason, microsoft will issue an update as quickly as possible. They need the LDR branches clean enough for the next service pack after all. (The link you gave had a lot of good information in it!) So, there are basically two choices to update Windows 7 Post SP1 properly. Either get the absolute minimum amount of fixes (mostly security updates) through Windows Update (about 40 or so updates) which keeps everything in the GDR branch, or go through the Repository and have a fully up to date system (about 300 updates) which makes a lot of components go to the LDR branch. At least I'm finally beginning to understand a bit of how the Windows Update system works. Between all the dependencies, multiple superseded versions, types of branches for the updates, etc, it can be complicated...
?? -"beige Volvo", implying "boring but safe".. IMO, this thread exists to share the very latest patches available. Running only GDR (if that were possible) seems to defeat that point. orbidia: I understand you want a reliable and stable system. And there are a lot of people here who are using these patches who also want stable systems. If a flakey patch were to make it into the repo, somebody would mention they're having problems and it'd eventually get removed or its proper install sequence would be learned. The LDR branch is not untested, as you said. They haven't been tested as thoroughly as GDR, but they do go through testing before being released. Hotfixes in general aren't tested as rigorously as an update available through Windows Update, but they all go through some amount of testing. My point being, you should feel comfortable running the latest batch of LDR updates, knowing that if a problem were to pop up, that we as a group here will try to find a solution. Regards & Happy Holidays to you.
Well like I pointed out in SoLoR's update list, the majority of the updates are LDR only now. For the GDR+LDR updates, the GDR update doesn't include many of the fixes of the superseded updates you may have already removes, so it kinda defeats the purpose! Whilst its true there may be an issue with an LDR update at some point in time, you have to remember that almost all issues with an update are picked up in the testing that they do end up doing. If there is a minor glitch, it may or may not be picked up in rigorous testing. Some may argue against that point, but I would then have to remind them the USB driver fiasco after SP1 installation! Service packs, apart from actual Windows releases, are probably the most rigorously tested software around, and yet that still failed to get found. Of course, not to mention the other bugs that there are fixes for
Well, like I was just pointing out its a bit hard to avoid LDR using the repository... you'd only be able to install half the updates at most, and make sure you don't have any superseded or partly superseded updates installed, otherwise you are bound to get some 'LDRness' For an update that has both GDR and LDR versions, the LDR version has probably gone through just as much testing... even if this is the case, remember the LDR branch is a culmination of previous GDR branch fixes as well, so its just the pure LDR branch changes that are being tested. As its a cumulative branch, in a way, the testing is somewhat 'cumulative' as well the only thing then that would be needing testing the the compatibility between the changes, which again undergoes testing and is cumulative (its only the latest changes that are the least tested)... if that makes sense. That is oversimplifying it a bit, but the principle is sound Pointzero is correct in saying about reporting any issues with updates, its what forum discussions are for
@SoLoR In KB000000 you've left KB2603229 in the x64 main folder, and also in the Not integratable to Offline image folder. So please leave it only in the Not integratable to Offline image folder next time you upload KB000000.
Hello I have two questions: 1) Why can not I download this file? ...hotfix.chris123nt.com/Windows.7/Hotfixes/x64/Update.cmd when I click to download the file this message appears: 404 - File or directory not found. 2) I tried to download some updates on the site but the links are wrong: ***updates.mihgroup.eu.org*** -> column X64 *hotfix.chris123nt.com/Windows.7/Hotfixes/x86/NFS/Windows6.1-KB2580164-x64.msu *hotfix.chris123nt.com/Windows.7/Hotfixes/x86/IIS/Windows6.1-KB2646735-x64.msu *hotfix.chris123nt.com/Windows.7/Hotfixes/x86/IIS/Windows6.1-KB2597665-x64.msu *hotfix.chris123nt.com/Windows.7/Hotfixes/x86/IIS/Windows6.1-KB2467528-x64.msu Look at the above address (x86) rather than their x64. And the file is x64!!! The right way is: *hotfix.chris123nt.com/Windows.7/Hotfixes/x64/IIS/Windows6.1-KB2467528-x64.msu Thanks.
I think there is something wrong with the .cmd file link, yes. If there was something wrong with the other links, it looks like it has been fixed now because now the links on the updates.mihgroup.eu.org page seem to be correct.
this is known already, i just dont feel like buging chris123nt just for this it was copy/past sloppiness i fixed them
Hello, I downloaded and installed all updates for Office 2010 x64. But Windows keeps asking for an update: kb2553270 -> proofloc2010-kb2553270-fullfile-x64-glb.exe ***. microsoft.com / download / en / details.aspx? displaylang = en & id = 28528 I searched the site (hotfix.chris123nt.com) and did not find the corresponding file *.msp. See you soon.
Hi, KB2553270 contains 32 language specific .msp files and they're all in the repo. Look through what you have for files named proof-xx-xx.msp. The English language ver really only needs proof-en-us.msp, proof-es-es.msp & proof-fr-fr.msp, but if you're running a different language, make sure you have all of them (or at least the .msp file specific for your language, in addition to the other three).