Repo updated. Office 2010 repo will follow. I first have to investgate those files. Thanks pretty much to PointZero.
As the only change for 05 September is the new KB2506143, people can use the updated 03 Sep uninstaller I uploaded this morning as it already includes this change.
For people who still don't know the following point. KB2506143 can only be installed when the prerequisite .NET 4 or .NET 4.5 is installed first.
I have: Code: Package_for_KB2685811_BF~31bf3856ad364e35~amd64~~6.1.1.11 | Installed | Update | 8/17/2012 12:12 PM Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11 | Installed | Update | 8/17/2012 12:12 PM Package_for_KB2685813_BF~31bf3856ad364e35~amd64~~6.1.1.11 | Installed | Update | 8/17/2012 12:12 PM Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11 | Installed | Update | 8/17/2012 12:12 PM and Code: {78909610-D229-459C-A936-25D92283D3FD} | Microsoft SQL Server Compact 4.0 SP1 x64 ENU {1AD147D0-BE0E-3D6C-AC11-64F6DC4163F1} | Microsoft .NET Framework 4.5 {1D8E6291-B0D5-35EC-8441-6616F567A0F7} | Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 {ad8a2fa1-06e7-4b0d-927d-6e54b3d31028} | Microsoft Visual C++ 2005 Redistributable (x64) {A4E269C1-168D-40D3-9ABD-57FE4D4DB537} | Microsoft Sync Framework 2.1 Core Components (x64) ENU {F0B430D1-B6AA-473D-9B06-AA3DD01FD0B8} | Microsoft SQL Server 2005 Compact Edition [ENU] {F0C3E5D1-1ADE-321E-8167-68EF0DE699A5} | Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 {5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4} | Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6276 {31E8F586-4EF7-4500-844D-BA8756474FF1} | Windows Automated Installation Kit {AC76BA86-7AD7-1033-7B44-AA1000000001} | Adobe Reader X (10.1.3) {9BE518E6-ECC6-35A9-88E4-87755C07200F} | Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6276 {3E06CDF6-FC15-3137-A625-C21A8EEAF83A} | Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.50727 {23170F69-40C1-2702-0925-000001000000} | 7-Zip 9.25 (x64 edition) {BA035DEA-E9C0-429A-95D6-1986C12142DC} | Microsoft Sync Framework 2.1 Database Providers (x64) ENU {710f4c1c-cc18-4c49-8cbf-51240c89a1a2} | Microsoft Visual C++ 2005 Redistributable {85467CBC-7A39-33C9-8940-D72D9269B84F} | Microsoft Visual F# 2.0 Runtime {3A9FC03D-C685-4831-94CF-4EDFD3749497} | Microsoft SQL Server Compact 3.5 SP2 ENU {89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} | Microsoft Silverlight {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3} | Microsoft SQL Server Compact 3.5 SP2 x64 ENU {CCA5EAAD-92F4-4B7A-B5EE-14294C66AB61} | PlayReady PC Runtime x86 {E313BDBD-426C-3FC7-A085-07BA9EC6FA87} | Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.50727 {9890E3FE-F661-3A95-92B5-62B3312C7787} | Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.50727 {BCA9334F-B6C9-4F65-9A73-AC5A329A4D04} | PlayReady PC Runtime amd64 {A420789F-926D-3CC1-976F-EA60683BF78F} | Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.50727 {1391A7DF-8A20-44C0-A4D8-0D23DDA1C627} | Microsoft Sync Framework 2.1 Provider Services (x64) ENU in a sysprepped image-no .NET 4.0 anymore, just 4.5. I am going to install KB2506143 tonight in sysprep. You should have no problems saving it in a prepared image.
I agree with RickSteele about leaving them in (I haven't experienced any problems). But since others do have problems, I think everyone will understand if you remove them. By the way, I've installed the latest official 12.8 AMD video driver but since my card is old (a 4850), the Catalyst driver version shown as being used is 12.6.
Ok, more feedback again regarding the explorer restarting issues & KB2685811 and KB2685813. * I'm now definetely sure that on my system NO solution is good if I want to use the latest drivers. Both GDR/LDR and also integrated, in all three situation these problems appear * I've been able to replicate them also on a Dell Vostro 3300, with Intel chipset drivers and Nvidia video drivers. My first system that had problems was a desktop one with AMD chipset and video drivers (12.8) * In the past I didn't encounter any problems if I integrated those. This is not the case anymore. I've also been issue-free for a day and a half on my system that just doesn't have them. So in my opinion these updates should be either removed, or moved to an additional folder, so for example in McRip's case, most users that just install/integrate the updates from the archive will be safe from such issues. Also, I really don't understand why some people make suppositions on why this updates are not to blame and make another bunch of suppositions on why they're needed. I have some questions for them and of course for anyone who can give an answer about the ''usefullness'' of these two updates. 1. Can you name 1 (ONE) windows 7 driver that needs these updates? Sidenote: Fresco Logic latest windows 8 USB 3.0 driver still uses (has it packed with the .inf) WdfCoInstaller01009. 2. Can you name 1 (ONE) drivers that won't install without these updates? 3. Can you name 1 (ONE) driver that has such windows .msu updates also packed in their driver install packages? (second option from below). Sidenote: Here are some quotes from what Microsoft is instructing driver devs (link here): I've only encountered drivers that had the WdfCoinstallerxxxx.dll packed with the driver setup app. NONE that had the msu package. And I don't think that a driver dev is stupid enough to rely on Microsoft update, when the only thing required of them is to also pack the WdfCoinstallerxxxxx.dll and pre-solve potential issues. As a short conclusion, only WdfCoinstaller01011.dll will be really needed in the future (I haven't encountered ANY windows 7 driver that uses this, and also found a single windows 8 driver that still uses WdfCoInstaller01009), and it's 99,99% likely that drivers that needs those WdfCoInstaller01011.dll will also pack them. So once again, why are those updates needed?
Simply logic: The updates are only used if a driver calls for their need. If you are having issues with a certain driver and having these installed, the the driver must be using them to cause the issue. The issue is most likely caused by the driver only having beta Windows 8 support, and any issues should be rectified in the near future (if they haven't already). For instance, Catalyst 12.7 which someone mentioned was an issue, is officially outdated, 12.8 is the current driver which has better Windows 8 support. Further to that, there is a new driver series currently in beta (actual driver 9.00, not 8.982 like in Catalyst 12.8), which further extends Windows 8 support. In any case though, like I was saying they are only used if required. Also they replace 1.9, and aren't 'an optional component', in all likelihood at some point in the future they will be pushed through Windowsupdate.