i did not stop scaning, this are only ones avilable and no no new .net 4.0 this week... question to komm: where you get this updates? you have access to payed support for companys?
All updates I marked with 'X' in my updates list can be installed on any!!! (starter to enterprise) version of windows. This makes sense! MS has implemented "any time upgrade". So if a user upgrades to a new windows edition, the updates necessary for this edition are already installed. If you try to install the .msu file installation of updates may fail! But the update will install if you use the update.mum and/or updates-bf.mum after extraction. dism /online /Add-Package /PackagePath:"%updir%\%%A\update-bf.mum" dism /online /Add-Package /PackagePath:"%updir%\%%A\update.mum" If you check, for example, a VPC installation on a starter edition you will see, that the State of these updates is Staged. That means, the update is installed but not active. It’s just waiting for the feature/addition to come active.
I should point out Windowsupdate will show updates that have had the GDR (when LDR is present) component removed that are normally listed on Windowsupdate. This is also the case if you just install the LDR version and not both LDR and GDR. The updates will serve no purpose and can be hidden. If anyone knows how to hide them outside of Windowsupdate (like a registry setting...) I could add that to the script.
There are only a few(7) gdr's to keep, I added them to KUC, KUC-State: OK/GDR; ADD/GDR 2446710,2545698,2547666,2619339,2633171,2539635, 2656356 Interesting i find out that you should also keep the LDR version of 2478662. What about 2601456? I don't understand what you mean with "causes windows to revert changes". Plz explain.
I could easily set it up so it won't skip those updates on the removal (and add them even for just LDR install), what do people think? When I uninstalled the GDR version of KB2601456 , upon reboot the finalisation part of the update process only gets to 7 percent then it comes up that it failed and it reverts the changes (including all changes from the removal of the other updates). I'm not sure why that is, and it may only be the case for me or some people, but I suspected it was due to it being for acpi.sys and machine.inf. Try editing the script and see if its the same for you if you like Change: if /i %kbf% equ KB2601456 goto :eof to rem if /i %kbf% equ KB2601456 goto :eof
I think that would be good, but, perhaps, if possible, leave removing GDR as an option for those of us that want as little as possible showing up on M$ update.
It'd be convenient to have GDR for those few that WU complains about. Previously, I've manually hidden those updates in WU after using SoLoR's script. But if anyone knows of a way to hide those updates through a registry setting (as you asked for earlier) and then not have the GDR, that'd be a good option also. Either way is fine.
There are two versions Code: jscript.dll----5.8.7601.16982 jscript9.dll---9.0.8112.20544 KB2632503 should apply to the first and update it
I see! Microsoft did stuff up though the files listed in the KB article are not the same as those in the actual download. The actual download contains 8.0.7601.21838 (and the RTM & GDR versions), the KB article relates to the 5.8.7601.21838 script.dll file.