I'm surprised people using SimplixUpdatePack are actually interested in updating through WU... Just ignore it. Wait for Simplix releases. There's practically no difference between running WU once a month or downloading a pack of updates once a month.
Most of us (I think) use it to "catch up", not to replace. Especially those of us that use it for offline integration...
I noticed when I pass the '/Index=*' parameter, the program unpacks all the cab packages (default='%windir%\temp'), but after every index deletes the files and again unpacks the packages, wasting time. This adds up alot to the total time of integration and strains the drive, since in the end it might have written around 2.5GB. Is this a bug or are these package files different for every index? Is there a switch so it does not delete the unpacked cab files? Ofcourse this must not cause it to select packages for editions not applicable. Also is it a bad idea to use a SSD (such as the MX300) as drive for the process? I mean like will this process cause the drive's live to become shorter, like very very much shorter?
It is by design of Simplix, you simply could do only the starter (x86) or home basic (x64) index and afterwards offline upgrade them to higher sku's.
UpdatePack7R2-17.4.15.exe Source: forum.oszone.net/post-2729390.html#post2729390 Download: update7.simplix.info/UpdatePack7R2-17.4.15.exe Code: File: UpdatePack7R2-17.4.15.exe CRC-32: 6d7140da MD5: f0530bd8ae2c1435ebe103bc1e937ab4 SHA-1: b8ab3fba2b8f8e082b66b42d17c2a81c87c83776 SHA-256: 5fe2bb86f11ffa614e4e2ec36afe7bbe3162b54c4b442de5f33dfbfc30cb4d0e
Would be nice of the pack stop harassing me with the IE updates, before installing the rest of the package, this pack installed in 3 times, 3 restarts... or simply something i did not catch ...
UpdatePack7R2-17.4.20.exe Source: forum.oszone.net/post-2730992.html#post2730992 Download: update7.simplix.info/UpdatePack7R2-17.4.20.exe Code: File: UpdatePack7R2-17.4.20.exe CRC-32: 2c0951ba MD5: d1411321b0cb9209720b79f0422f5ca2 SHA-1: 26feb077b16c8d8dffe4679dc3eda4184597392d SHA-256: 8b05e5bda3d3660f712d915f42f6b09ac2a457e21192a567c3667c661ae246bb
Changes in version 17.4.20 Spoiler Changes in version 17.4.20 Added KB4014565-x86-x64 (replaces KB3210131-x86-x64) Added KB4015193-x86-x64 Added KB4015549-x86-x64 with disabling telemetry and processor checking (replaces KB2636573-x64 (Server 2008 R2), KB2676562-x86-x64, KB3062577-x64 (Server 2008 R2), KB3118401-x86-x64, KB3123479-x86-x64, KB3126446-x86-x64, KB3146706-x86-x64, KB3149090-x86-x64, KB3156017-x86-x64, KB3184471-x86-x64, KB4012215-x86-x64)
That's good. Will have to try it out. I think the previous may have been broke because I couldn't install a MS Hotfix. Tried clean install twice & it wouldn't install. Went back to my March build & of course no issue..
I'm very interested as to how well the the CPU check is disabled. Can anyone share their experience(KL owners)?