@Trinket - I tested shon3i & Burfadel initial vc++ runtimes on win7 sp1 x64 + solor's pack + net4 client + this reg key: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\6E815EB96CCE9A53884E7857C57002F0\InstallProperties] "LocalPackage"="C:\\Windows\\Installer\\10ce222.msi" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\67D6ECF5CD5FBA732B8B22BAC8DE1B4D\InstallProperties] "LocalPackage"="C:\\Windows\\Installer\\10ce216.msi" WU will not nag you about kb2538243.
Does anyone have the link to the Microsoft website where you can search for a KBxxxxxxx hotfixes and then add them to a cart. Then you go to the "cart" and then download the hotfixes? I was using it the other day and I lost the link.
burfadel: My understanding of the difference between your Installer for Win Updates script and SoLoR's update script is that SoLoR's only installs the LDR branch if both GDR & LDR exists, whereas yours installs both branches, thereby providing a clean pass for Windows Update (at the cost of a little disk space for the unused GDR files). I've been using SoLoR's script since I like to keep things as lean as possible but I see that you continue to improve upon and add logic to your script. Would it involve much effort for you to add an option to your script that would install only LDR, similar to SoLoR's? Basically, merge the functionality of the two scripts to get the best of both. Just a thought-- no worries at all if you want to keep your script as is. p.s. the link for the Runtime Installer above appears invalid at the moment.
Update KB2592546 was removed from the repo as not only had Microsoft removed its availability, but some were reporting issues with it not working properly. The feature adds support for the multithreading system on the Bulldozer (8 integer cores but only 4 FP etc), but was reported to be incomplete and only part of the update. Microsoft released it by accident (apparently)... Although this update is specifically for Bulldozer support, its still valid for every other CPU that previous versions were valid for as its just a support feature that was added to it. Since the updates are cumulative (the LDR version), it incorporates all previous changes made to the files since the original (in this case, SP1) files. When the update is properly release, its fully safe to run on Intel CPU's as well. Although Intel CPU's aren't the main focus of the update, depending on how the update is done and the efficiency of the current system, Intel users may see a fractional increase in performance too. This would be due to thread scheduling optimisations etc. When the update is finally released in its entirety, it probably won't be classed as a hotfix, I would be thinking it would be an update pushed through Windowsupdate.
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!