Since you use the .msp files, newer version simply have newer versions of the .msp files (such as word-x-none.msp). Since these files contain the files which are copied directly over the existing files, there is no need to remove the older updates. Its a little different if you use the base .exe files. This is different to Windows updates where even if the same files are update they may be completely different KB article numbers, and the files are stored in the WinSxS folder.
someone please clarify something with me, in a folder with both update.mum and update-bf.mum, which should actually be integrated first?
The older updates do take up disk space though, if not removed. Copies of current and previously installed .msp files are stored in C:\Windows\Installer. The file names are changed but look at the dates/sizes (or view file property details) and you'll spot them. Using Word as an example: I have 3 .msp files in that folder, each about 68MB, from when I've installed patches (word-x-none.msp) that updated to 14.0.6106.5000 (dated 6-12-11) to 14.0.6109.5000 (dated 8-16-11) to the most recent of 14.0.6112.5000 (dated 10-16-11). It seems a waste of disk space to retain the old updates. Those copies are in addition to the original install files in C:\Windows\Installer\$PatchCache$\Managed\00004109110000000000000000F01FEC. There are folders in there for the original ver of 14.0.4763 and the updated SP1 ver of 14.0.6029. Even though many of us do it, MS recommends not using the .msp's for updating after install. Look at the Note towards the bottom of this page: hxxp://technet.microsoft.com/en-us/library/cc178995.aspx#BKMK_MsftUpdate The .msp install method works well during the initial install of Office (via the \Updates folder). But for updates installed afterwards, I wonder now if it might be better to just use the full hotfix installers (.exe) to be able to make removing superseded updates easier. Not 100% sure about this though..
yes i noticed that, but since integration does not error out i didnt put it there... i might however move it... ill see... i think best would be to have it on both places...
If you want to clean out some of the old updates but don't see them listed as uninstallable, try this command: msiexec /package {product_code} /uninstall "full_path_to_.msp_file" /qb For example, this is the command I used to remove the oldest word-x-none.msp update noted in my previous post: msiexec /package {90140000-0011-0000-0000-0000000FF1CE} /uninstall "C:\Windows\Installer\1042ea.msp" /qb The tricky thing is determining which .msp's in C:\Windows\Installer to uninstall. I used file property details to look at descriptions, along with sizes and dates to find what looked like superseded ones. If you're not sure what the product code for the ver of Office you're using is, take a look in: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Common\Config\ That location is for 32-bit Office on 64-bit OS; if you've got 32-bit OS, it may be in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\Config\ More info on this is in: hxxp://support.microsoft.com/kb/903771
More on .msp updates bananajoj2- when the question is asked here which .msp's are needed for the \Updates folder, the common answer is "throw them all in and Office will only install what's needed". That is true, but here's something to think about. Setup looks at which Office suite you have and installs all updates applicable for that suite. But, if there are programs you choose not to install (but are included in your suite), setup will still install all applicable updates- regardless whether or not the program is installed or not. The updates are copied to the C:\Windows\Installer folder in case you install those programs at some point in the future. For example, if you have Office 2010 Home and Student, only Word, Excel, PowerPoint & OneNote are included in it so there aren't a lot of updates to apply to it. But if you have Office Professional Plus 2010, which includes Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Access, InfoPath, SharePoint & Lync, you may not have every one of those programs installed. Even if, say, Word was the only program chosen to be installed, all updates for the other programs will also be installed, leaving a lot of clutter on the disk and in Add/Remove Programs. If you install every program included in your Office suite, this is all a moot point and you'll want all the updates available. But if you normally only install a couple programs from a large suite like Pro or Pro Plus, you'll want to eliminate the updates for programs you don't intend to use.
Before I had to re-install, I was getting 30MB/s speeds. Now after my clean install & install of SP1, the max speed I get is 8MB/s.Do you know which updates improve USB performance? I don't wanna install all the updates, since it's what caused me to have to re-install windows.
I've integrated GDR+LDR, ie9, ldr placeholder and what i've noticed is that, my batch files appear to work slower, that is, going from one line to the next. there's something like 1-3 second delay per line when i tested a .wim without any hotfix, my batch file went a lot quicker, less than a second per line. does anybody have any idea whats going on?
I've also seen a random slow-down in a file-search program I use and the slow-down has just started with a recent re-install of all GDR+LDR. Based on our experiences, it might be worth backing out updates related to Windows Explorer (?) or to try going back to a GDR release for Explorer related updates. Not sure though.. Anybody else? Did you see what I suggested? Just curious- it may not make much of a difference, but then again, the option is called "Better Performance". hxxp://forums.mydigitallife.net/threads/19461-Windows-Hotfix-repository/page328?p=503967&viewfull=1#post503967
KB2603229: is this update merely a reg tweak? Or does it replace any files? If it is just a reg tweak, I will integrate it into my image rather than apply the update post-install.
It wont work because uses a EXE to do the updating of the registry entry, waik will not be able to mount the hive and run the exe for offline purposes. The best thing to do is use something like regshot to track the changes and mount the specific hive then apply the changes manually If you do that there will be no need for the hotfix at all
I'd be happy to test this, but I can't reliably reproduce the problem. It just happened randomly (and only a couple times). As a side-note, I was using a beta Catalyst driver for a week or so, but replaced it with the official release yesterday. That driver was causing other issues so it may have been the culprit for me. But if you have a test-version of your batch file, you could send it to me and I'll try to help narrow things down.