Search the Community
Showing results for tags 'integration'.
A long time ago (2008) I've created two tools for Windows XP for integrate Windows Updates into XPCD http://www.msfn.org/board/topic/117189-windows-xp-service-pack-3-integration/ http://www.msfn.org/board/topic/140031-windows-xp-hotfix-integration-tool-wsp4-112009 And now, I present you my new creation Since there was no SP2 for Windows Seven yet i started my own Project named WindowsPatchLoader. I know there are a couple of tools that do the same job. BUT i wanted my own tool. I wanted just "re-invent the wheel". All Updates you download are from Microsoft. [Windows Update Method] windowsupdate method is like Windows Update and it's always up-to-date, depends which Microsoft Software/Update you are currently installed. I'm getting the Updates/Urls from Windows Update. Hotfixes are not stored anywhere. [Other Update Method (from Wsusscn2.cab] There is also an alternate method to getting Updates for other systems while i am not able to scan other systems than installed one. Wherein i used text-files on my server to save all urls from wsusscn2.cab. All urls are also from Microsoft. These files are updated weekly. This Method was my first idea before beginning to write this tool. As well as Windows Update too hotfixes are not stored anywhere. But i do not recommend this Method while wsusscn2.cab does not contains all Updates. There are only "critical" and "security relevant" updates. [Filter] Downloaded Updates Broken Updates Filter .cab and .exe files [Export] Download Links: to export all download links Superseded: to export superseded updates [updates Cleanup] creates new folder with newest updates [Categorized Patches] downloadeded patches will be copied in categorized folders with newest updates you must to put all updates in same folder. [Exclude] to exclude selected updates [KB Support] to get more Information about selected update on Microsoft Knowledge Base [import/Export Update List] you are able to safe update lists support for Windows Hotfix Downloader Update List [Tools] Nvidia Driver: prepare nvidia files for integration MSU->CAB: extract msu files for integration EXE -> CAB: extract i.e. Internet Explorer for integration CAB -> MSP: extract cab files to msp (office updates) [integrate] you are able to integrate updates to windows dvd. This Tool requires DotNetFramework changelog: v1.0.14 add cab to msp (outlook updates) minor fixes changelog: v1.0.12 new: import/export update lists minor gui changes Download WindowsPatchLoader v1.0.14 WindowsPatchLoader2.0.exe (compiled with DotNetFramework 2.0) MD5 288fc9578bc8bdca17c8b74600ca4eda SHA1 1581867ab5898c33196087e81f94167fa33d1a4d SHA256 77700b359eb8ab76b27cf60ee0eeab4feff565f20b286353c4e950569a3a353b WindowsPatchLoader.exe (compiled with DotNetFramework 4.0) MD5 25eb6f34b4a26b1853e911c8e11aae94 SHA1 09117e106be501190f3889fba97e61a826787cdf SHA256 2bd02547f148a77a520ad07a48becf81b328b3dd2dc6a50e08976d6ed98c7862
I have two doubts: 1. Does KB3172605 (July 2016 update rollup) replace KB3156417 (May 2016 update rollup)? 2. Integrate KB3170455 (update for Windows Print Spooler)? Supposedly it stops non-admin users from installing a network-printer :/ What set of updates is the best to integrate (KB in exact order): KB3020369 kb3125574-v4 KB3168965 KB3172605 KB3020369 kb3125574-v4 KB3156417 KB3168965 KB3172605 KB3020369 kb3125574-v4 KB3156417 KB3168965 KB3170455 KB3172605 ? KB short descritpion: KB3020369 April 2015 servicing stack update for Windows 7 and Windows Server 2008 R2 KB3125574 Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1 KB3156417 May 17 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 KB3168965 July 12 2016 Security Update for Windows Kernel-Mode Drivers KB3170455 July 12 2016 Security Update for Windows Print Spooler Components KB3172605 July 21 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
Hi nuhi, Not sure if this question has been asked and answered. How does NTLite driver integration interact with Win10 installation? Assuming Win10 has built-in driver, but an old version. Then after integration of a newer version of the driver. What would happen? 1. Win10 install build-in older driver, then update to newer driver during installation process 2. Win10 just install the newer driver from integration, and ignore the older built-in ones? Or none of the above? TIA