Glad to hear. yes that could explain what happened but the problem shouldn't have occured because i don't see how integrating drivers into install.wim can prevent the updates integration to be done using simplix Pack but it seems to be the case from the tests you did.
everything worked perfect now.. Just do the updates first and afterwards the driver integration... i now have an up to date iso with all drivers... Im happy as i can get now.. Thanks for the support
but you know atak's tool allows to integrate the updates and the drivers at the same time, i've tested it and it works.
yeah, but i wasnt shure what updates the tool was downloading..I wanted to be shure that NO telemetry updates and such are present, and as far as i could gather the infos, simplex was the way to go..so i decided to use the Update pack (simplex)... Anyway, im very thankfull for both tools and work.. Great stuff... Thanks again for all the infos and help... im off to bed now..i spent my whole day making an updated ISO, haha... GN8 EDIT: well, im stumped..i have to say, i never had a windows install that was running this great.. Props to the dev´s and users doing this projekt... I cant thank you guys enough.. WIN 7 Rules !!!
I have downloaded 17.12.15 from oszone. From all I've read over there, I think it's preferrable over 18.2.18, due to the mess of borked updates issued by M$ lately. However I can't seem to find any published hashes for verifying the file anywhere (apart from the ones given in OP, which are for 18.2.18 of course). I'd like to check the integrity of my downloaded 17.12.15. Any tips ?
From previoue OP message File: UpdatePack7R2-17.12.15.exe Name: UpdatePack7R2-17.12.15.exe Size: 702914008 bytes (670 MB) CRC32: FE52FC97 CRC64: A76C09A681C52E93 SHA256: 514938E870A1E6EA77C2DB17959CB9442B01EE5A9762472C5263049D8A01EC81 SHA1: 12362F261C0D77036ABFEE3FC5D4BFD35EFF9429 BLAKE2sp: 5B5B343DEECE562E26D3CC63997E5747F2F0CE9DEE56E3BCB76B159AECBD6059
^Yup. Those are the ones. CRC32: FE52FC97 MD5: D1DC32F662623E3097776F8397278D26 SHA-1: 12362F261C0D77036ABFEE3FC5D4BFD35EFF9429
@LifeIsNotEasy Thx ! @shhnedo Also thx, and BTW: a tiny detail on your screenshot prompted me to do some research and try to improve upon my paleozoic hash-checking .BAT file. I'm now using, not actually the HashTab tool you're using, but the slightly different HashCheck one. So, double thx !!!
@Enthousiast If I may ... I'd like to request / suggest that some additional info be added to OP. This is a result of a couple hours skimming thru oszone's thread for Simplix pack... 1. Clarify that 18.2.18 is NOT the version that the pack author recommends to general users, but rather a 'testing-like' build that has a significant probability of causing a variety of issues to users. [REASON: after the recently disclosed Intel bugs, MS has issued a succession of half-assed patches - I even learned (elsewhere) that, going into March, there's already a patch for a patch for a patch.] Among the groups of users more likely to be hit by bad patches (some of which are already included in 18.2.18, if I got this right) are owners of some specific generations of AMD processors. There are others, but sifting thru Google-englishfied Russian posts is very tiresome and frequently misleading... so I can't be much more precise here. 2. Add back the link(s) to 17.12.15 and, conversely, clarify that it is the latest version that Simplix himself feels comfortable to support, for the very same reasons above. I ask that you give some consideration to the above. Cheers, and many thx for maintaining this thread !!!
There are even Windows 7 machines (I have three without SSE2 support) that cannot swallow any of this year's updates, so far. As soon as any is installed, the machine doesn't boot at all (no STOP BSOD at all, just black screen at very early boot).
Over the years I've had so many more problems caused by bad Windows updates than by viruses or malware. In the words of Pogo, "We have met the enemy and he is us".
Just open the existing iso with something like PowerISO and replace the install.wim, save the changes. No need to extract the iso and make a new one.
Oh, great ! Thanks twice - 1st for confirming I was on the right track with the pending tasks, and 2nd for the suggestion of PowerISO. I investigated PowerISO (plus a number of would-be replacements). PowerISO itself is a commercial product, which would require me to either purchase a license or circumvent it - both things that I'd rather avoid if possible. There's also a number of other products with more or less similar features, all of which failed to inspire me to even test them ... My current setup includes an ancient copy of 'Virtual Clone Drive', thanks to which the original ISO file is kept mounted with its own drive letter (even accross reboots). ImgBurn is another tried and true friend of many years; I may lack the experience of creating new bootable media with it, but the tutorial I just linked to looks promising as to bridging that gap. So, my current plan to finish this involves two brain-dead operations (copying the mounted ISO contents to a temp folder, and replacing the install.wim there), plus a mildly tricky 3rd and last one (burning the 'edited' contents onto a new ISO with ImgBurn, while also making it bootable as per the tutorial). Failing all that, I'll then reconsider PowerISO for sure ! Cheers m8
Extract ISO, make changes on folders or files -> Use imgburn to make a new ISO. Check Youtube. "How to burn bootable iso with imgburn" or something. It's easy. GL HF