Uncompressed VC++ runtimes x86/x64 have been updated on McRip's Cesidian Server to reflect KB2618543.
Use 7zip to extract the msp you will find the "redistributable" runtimes Code: FL_vcredi64_exe_133333_133333_x86_ln.3643236F_FC70_11D3_A536_0090278A1BB8 FL_vcredist_x86_exe_132136_132136_x86_ln.3643236F_FC70_11D3_A536_0090278A1BB8 FL_vcredx64_exe_133334_133334_x86_ln.3643236F_FC70_11D3_A536_0090278A1BB8
The 2008 runtimes don't install; only 2005 and 2010 using v13; see Runtimes_v13.jpeg. If I run the install.exe from each of the non-debug 2008 redistributables they install correctly; see Runtimes_2008.jpg.
Fails because its not set as admin install package in summary info, plus you forgot the wufix Edit: @RickSteele why did you not just rename the files to add .exe, they are the actual installers
Righto', will do that straight away; thanks. "Fails because ...." is for Burf' to fix...correct? Thanks
Is there a good reason why the KUC Remove_OLD.cmd file includes files that are in the Uninstall Pending state? Dism says they are not present if you try and remove, so I was wondering why they are included. For example, all my IE8 files are in Uninstall Pending, because I have IE9 in the wim. I'm using an offline image for my processing. Al
KUC is getting rid of the superseeded-pending or installed. I saved that part of his cmd that addresses the old IE8 files, loaded up my image in sysprep on a VM and ran the cmd. IE9 is installed and all IE8 files are no longer part of the image-and IE9 is uninstallable.
I am new to the forum but not to using various tools and the SoLoR packs... after testing a few dozen integration's with the WIN7 Toolkit I have a few questions that I just want to check on: Am I correct that these 3 updates which show in MSU are errors on MS part? Security Update for Windows 7 for x64-based Systems (KB2556532) Update type: Important Security Update for Windows 7 for x64-based Systems (KB2644615) Update type: Important Update for Windows 7 for x64-based Systems (KB2639308) Update type: Recommended When I hide KB2639308 another update shows: Update for Windows 7 for x64-based Systems (KB2534366) Update type: Important When I hide that one KB2534366 another one shows: Microsoft .NET Framework 4 Client Profile for Windows 7 x64-based Systems (KB982670) Update type: Recommended When I hide KB982670 no further updates show... is this known behavior? KB982670 did not show once I added the Rick's DotNet 4 client package.
@compstuff refer post #4664 by SoLoR a few pages back in this thread: "Currently all hotfixes that shows on WU after applying pack, can be safely hidden because they are superseeded." "KB982670 did not show once I added the Rick's DotNet 4 client package." This is the correct update.
That's a weird one- I don't see any updated files that it'd install from PATCH_CAB and in !_StringData, it says "For Testing Purposes Only". It'll be interesting to see what the KB article says, when available (or if the update will even remain available publicly). Good find though Burf!
The KB article is avaible but I can't post the link...yet I don't have the required 20 posts) Issue that this update fixes When you install Office 2010 SP1, SharePoint Workspace 2010 is installed. However, SharePoint Workspace 2010 is not included in the original Office Professional Plus 2010 installation and should not be installed. In certain situations, Microsoft Office Groove 2007 is upgraded to SharePoint Workspace 2010 when you install Office SP1. For more information about this issue, click the following article number to view the article in Microsoft Knowledge Base: 2612800 Office 2010 SP1 installs SharePoint Workspace So allegedly it fix the god damn SharePoint Workspace issue when SP1 is slipstreamed! It is about time MS do something about it! Looks like they heard us!
Burf, you ask some good questions- maybe others know the answers. I'm not 100% sure how the update works at this point.. Yeah, it seems like this should've been an issue that was fixed a week or two after SP1 was released, instead of taking 8 months to do it. But, good timing, considering we were just talking about the issue here last week!