Yes that true, integration is different because the updates are committed straight away and not added to the pending list. Integration is still something on my 'to do' list (he says sheepishly). On the plus side, the autoreboot feature is great for those that don't integrate . Actually, if post Windows install setup isn't explicitly time sensitive, the autoreboot feature is probably more realistic to use than integration, especially for single machine installs, since it saves making a new image. BTW the test installers are testing the principals etc. The description is yet to be changed, and the warning message will probably get some tweaking before the final V24.
sorry for this late answer. I checkt 2446710 on my x86 system. If I uninstall it, windows still offers the update for installation. How do I test? I uninstall the GDR to keep or LDR to keep updates und run Windows update to see what it offers.
I see the komm's list some updates that I don't see in the SoLoR's repo (ex: 2649909-v2) is this normal?
Did anybody try to install a new version of Intel’s Rapid Storage driver or ATI's graphic drivers after installing 2656356? I had a problem with both of them on my TV-pc. The Intel driver always gives me: the setup program failed to install one or more device drivers. I made many changes, so I really do not know the exact reason why it worked at least. Definitely, the issue had something to do with the .Net installation. The last thing I did was uninstalling 2656356 and uninstalling the existing Intel Rapid Storage. After that, Intel’s driver installs fine. In addition, the installation of the ATI drivers made no problems than. P.S. The problem occures with the setup program. The manual installation of the Intel driver worked.
Oops, my mistake regarding 2561821 vs 2649909. Still, its not an update that you can 'install'. In terms of other updates, it seems Microsoft is primarily bulk releasing them now, going by the pattern over the last several months.
That's understandable Has anyone else tried the autoreboot feature, and if so, has it automatically rebooted, installed, rebooted, and repeated until all updates installed? If not, have you: - a Windows logon password? - UAC turned on? If the above isn't true for you, and it still doesn't work, please describe the issue you are having.
It should do, I did take that (and similar scenarios) into consideration. The data for the installer is kept in the user's documents folder, and since it uses option 2 (up to 50 updates at a time), the previous session of Windows temp folder is not needed. In fact, if the cabtemp folder exists after restart the installer will automatically clear it before starting again.
Sorry, I can't help you there. I only do offline integrations and install directly from disk, so my system is always up-to-date when I build a new one.
ricktendo64: Windows Hotfix repository created in Windows Server Update Services (Windows 2008 R2)? i wont create my Windows Hotfix repository.
The 'Windows Hotfix Repository' of SoLoR's contains all available non-superseded (that means it does not contain updates whose changes have been included in a newer update). The Windows Server Update Service (WSUS) contains only the general release updates, including those for Server 2008 R2 that aren't in the repository (since the repository doesn't include Server 2008 R2 specific updates), pretty similar to Windows Update repository. What this means is, there are a great number of valid updates in the repository which aren't in WSUS. The updates in WSUS that are also 'applyable' to Windows 7 are included in the repository (or a newer version exists in the repository) but not all the updates applicable to Windows Server 2008 R2 are included in the repository. I hope that makes sense! Basically: - if you are running Windows 7 and want a really update to date system, use the repository - if you are running Windows Server 2008 R2 use the repository, and then the KUC updater for the remaining Server 2008 R2 updates - if you just want a standard up to date system according to general release updates (WSUS or Windowsupdate), then use WSUS/Windowsupdate If someone can explain that better, which I am sure is possible! please do so!