if I ask, is that I found nothing on google you love google very well, to talk to each I will expect, that Solor is the time to give info
To you guys that posted about the .NET links snafu, Thanks; very good to know and I will remember. I am late getting back because I've been fighting with sysprep.....for 3 days.... Thanks very much again
i have exactly that much info that everyone can find out for them self if they extract it and open manifest files.
Here's the information I was able to get concerning the undocumented hotfixes: KB2472264 (Superseeds KB2477730)--> Arp.exe, Netstat.exe, Finger.exe, Mrinfo.exe, Route.exe, Hostname.exe, Tcpsvcs.exe, Bfe.dll, Ikeext.dll, Netevent.dll, Nshwfp.dll, Netiohlp.dll, Fwpuclnt.dll, Tcpip.sys, Fwpkclnt.sys 6.1.7601.21645 KB2462182 --> Stobject.dll 6.1.7601.21661 KB2507840 --> Ncrypt.dll 6.1.7601.21666 KB2496820 --> Vwififlt.sys, Vwifimp.sys, Vwifibus.sys 6.1.7601.21648 KB2462374 (same as KB2459492) --> Windowscodecs.dll 6.1.7601.21624 KB2502789 --> Ulib.dll, Ifsutil.dll 6.1.7601.21650 KB2496744 --> Erata.inf 6.1.7601.21659 *Note*: File version are taken from x64 hotfixes. Hope it helps.
I'm not referring to anyone in particular with the following, just giving a general idea of which is what Since Windows 7 and Server 2008 R2 are on the same direct codepath some updates may be for issues that only affect Windows Server 2008 R2, or Windows 7, but not both, however the files updated are common to both operating systems. For the purpose of the inquisitive, enthusiast, or just for those that want to be 'up-to-date', installing such updates is fine. You will know whether the update isn't applicable to your system because the update will tell you! If the update appears to be applicable but isn't, it means either you are using an update from the wrong service branch (such as a RTM only update on SP1), the update isn't applicable to your Windows type, in that it is only applicable to Server 2008 R2, or Home Premium if using Professional etcetera, or you are trying to apply an update that updates a component which you don't have installed. Preferably for the inquisitive, enthusiast, or 'up-to-date' group, the LDR versions are installed over GDR versions, even if the LDR version conditions aren't met. For everyone else, Windowsupdate should be just fine unless you are experiencing issues resolved by specific updates. Its not unreasonable to want to know what is updates with hotfixes, SoLoR does a good job of mainting the table below the hotfix changelog/commitlog, and the files updated/target of the hotfix does give you a decent idea of what the hotfixes actually do.
SoLoR had an issue uploading the new Office packs, the Office x64 updates dropped out at 18.2mb out of ~300mb when he uploaded it. The file in the repository is still the 18.2mb corrupted file. He also had problems uploading numerous individual files.
I see. However, LDR packages contain "other" fixes that have not undergone as extensive testing as GDR. Thus, installing LDR may lead to problems in Windows. Yes, I know. The probability of problem caused by installing LDR is so low that it is similar to that of striking a lottery. Nevertheless, I will follow what you guys have advised, which is performing backups before installing such hotfixes.
Actually GDR release pertains to the hotfix in question, whereas LDR contains fixes for that hotfix and all previous fixes relating to other hotfixes that affect a file. If you installed one update from the repository, and then installed another update that affects the same files, the second update will install the LDR version of the update. Since the first update is technically superseded, it is removed from the repository. Installing the second update then will only install the GDR version, hence the fixes applied to the first update don't apply! The argument about 'as extensive' testing is partially false, since anything categorised as a hotfix falls under this category. Only updates released through Windowsupdate have had the 'more extensive' testing. To be more accurate, Microsoft only release a fraction of total updates to Windowsupdate, and thats where the extra protection comes in. Consider this hypothetical situation: You want to get a pizza for tea (dinner). There is a pizza place 2km away but you don't like their pizzas. There's another pizza store 4km away that make brilliant pizzas. Sure, you can drive 2km and get the ordinary pizza (GDR), but why would you want that when the best pizza around is only twice as far? The pizza store that is 4km away, your preferred pizza (LDR) is twice as far away as the ordinary pizza, By driving that extra distance, you run twice the risk of having a crash, but the risk is low, and overall you end up with a better pizza! Of course, the alternative is to get the pizza delivered, however its only the 2km away GDR store thats in your service area (Windowsupdate). Point I'm getting at is, if you are wanting to install all these updates, then the only real way to do it is to install the LDR versions yourself, its either that or install every update ever released for your service branch, whether its superseded or not, simply because the purpose of installing all the updates is to be... up to date! installing GDR version when there is an LDR version does not achieve this unless there is a previously installed update affecting the same files, which is most likely superseded. The files remain on the computer, leading to more clutter, longer update times... its really pointless, and the system outcome is the same in terms of the files used by Windows. If the 'extensive testing' argument worries you, then you should stick to Windowsupdate. I'm not saying this as a criticism, just being realistic as there is no basis for a GDR over LDR situation when you're installing all these updates !!! Hope this makes sense The repository is a collection of all available non-superseded updates and hotfixes. It is NOT just a collection of Windowsupdates, hence the LDR argument is fully applicable when it comes to this repository!