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.
If no drivers use WDF, then there should be no harm in having them installed or not. Just like any updates in the repository, it is up to the discretion of the person installing them whether they want to use them or not. What suits one person doesn't mean it suits everyone else using the repository, such as not installing these two updates. If these updates are causing issues with you, and you don't know which driver is causing it, then it makes common sense not to have them installed. If you do know what is causing it, seeing if there are later drivers may help to resolve the issue. If a driver uses WDF, you can supposedly use the Windows 8 driver if you have these two updates installed (well, the Kernel mode update). In general though, you should be able to install it fine on a live system. Integrating it might be more of an issue as not all updates play nice doing this.
The scan on Sunday will be canceled. Probably it will be on Wednesday if everything will work out as expected. Two of my hard disks got broken and I lost all of my data. Yesterday I purchased new hard disks and now I am installing all the needed software. It's all f_cked up because I have to get all the software again.
Everyone will if they're installed Komm used the sensible approach to these updates. Give it a couple of months and these issues won't be a problem closer to/after Windows 8 is officially available and Windows 8 (and hence WDF 1.11) support is in full swing.
Registry Entries I was wondering if I could get some clarification on the registry entries that are being added/used for associated hotfixes (not tweaks etc). I am about to make a new integration today and was going to use: 2732072 enable.reg, 2743013.reg and KB2668751.reg Is this correct and/or am I missing any?
MS FixIt Info This question is similar to my registry question. I was wondering if I could get some clarification on the MS FixIt entries that are being added/used. I am about to make a new integration today and was going to use: MicrosoftFixit50470:: MicrosoftFixit50531.msi:: MicrosoftFixit50688.msi:: MicrosoftFixit50848_KB2665946:: MicrosoftFixit50877.msi:: MicrosoftFixit50897:: MicrosoftFixit50907.msi:: MicrosoftFixit50908.msi:: Is this correct and/or am I missing any?
Thanks to komm for the findings. Office 2010 Updates 2012-09-08 x86: kb2428677-x-none.msp 14.0.6126.5000 mso-x-none.msp 14.0.6126.5000 oobe-x-none.msp 14.0.6124.5000 osetup-x-none.msp 14.0.6124.5000 publisher-x-none.msp 14.0.6125.5000 word-x-none.msp 14.0.6126.5000 -------------------------------------- x64: kb2428677-x-none.msp 14.0.6126.5000 mso-x-none.msp 14.0.6126.5000 osetup-x-none.msp 14.0.6124.5000 publisher-x-none.msp 14.0.6125.5000 word-x-none.msp 14.0.6126.5000