RicaNeaga

Yes, I have some suggestions: 1. The latest usable versions of Renesas drivers for integration purposes are 2.1.28.0 for ''nusb3''-like drivers / 3.0.16.0 for ''rusb3''-like drivers. Why am I saying usable? Because these are the latest versions that are fully Microsoft signed. Newer ones will give you errors if integrated, but if you want to have the latest ones, install them AFTER in windows (after the install process is done). 2. If you use Win Toolkit to integrate them into the windows image, also check the advanced option from AIO to also integrate the USB drivers in boot.wim

Great to see you're back! Hope you won't mind, but I'll try to help you by making a list of stuff that users need fixing ASAP. I think such a to-do list that you can prioritize is required since you're time for this project is obviously limited. And on top of that list is support for the new updates database method developed by burfadel and abbodi1406 - see here. Such a method, that gets the hotfixes directly from Microsoft servers, via a .xml list with the Microsoft links, will be server-issues-free (unless Microsoft decides to modify at some point the links for the hotfixes, but that's unlikely), but I think will require some extra stuff from your app. For example, the hotfixes are archived by Microsoft, so it would be fantastic if Win Toolkit unarchives them directly after download, and deletes the archives, saving on the disk only the hotfixes. I'll also leave a post there, but please also contact them yourself, Lego.

I had the ''oportunity'' to test this installer on various builds and I can say something for sure: the errors when used alongside Win Toolkit (/y switch, runs normally dring first boot) are ALWAYS happening on x64 builds and NEVER on x86 builds, and also ALWAYS for 2005 and 2008, and never for 2010, 2012 and 2013. Moving it as (one of) the last installer(s) doesn't help (I know I said that, but I was mistaken, I confused it running great on a x86 build when moved last to also run great on a x64 build, which clearly isn't the case). Don't know if it helps with something... just pointing out the behaviour. Hope however at some point this great addon becomes usable on any x64 build made with Win Toolkit.

Are you joking??? They're in the first post linked.

Didn't know that, thank you for confirming. I'll update it every month (the complete archive) until another ''open-source'' alternative is online. I don't recommend KUC for offline integrations (especially with Win Toolkit), only for online (live) installs. Also KUC isn't up-to-date, last it was updated in october.

please post your config file (last session .ini)

Until McRip is back, here you can download archives that are up-to-date with all the needed security updates AND hotfixes (for windows 7 SP1 images)

VC++ 2012 Update 4 - released today.

Thanks, Etz! mooms - Again, about KB2574819 - Microsoft is now offering RDC / RDP 8.1 client funtionality under the KB2830477 ''umbrella'' (KB2574819-v2 (prerequisite), KB2830477 (RDC 8.1) and KB2857650 (RDC update)). So I really think you need to move all the three above updates to the not integratable folder, and also delete the superseded RDP / RDC 8.0 updates - KB2862019 and KB2592687. btw, RDP 8.1 is client only, for people looking to install the host for RDP 8.0 they have to also install KB2592687 (RDP 8.0), hopefully WU won't offer also KB2592687 after RDC / RDP 8.1 is installed.

I've neved had problems with KB2574819 either, but there are at least 3 users that solved their ''Win Toolkit runs too early'' problems by moving KB2574819 to the silent area. Look here and here. I'm always trying to be on the safe side... LE: And thanks for the MU.zip, looks promising, I'll try it on the next build, hope it doesn't overwrite my autounattended option to ''never check for updates'' WU default option.

Weird. Are you using some kind of autounattended .xml file, with install options, that you add to the windows 8.1 iso via Win Toolkit?

Maybe I'm confusing smth, I don't exclude it, but I really remember that both versions of the mass storage Intel driver (enterprise and normal) are usable for a X79 motherboard, all you had to do is choose an option in the BIOS. For example, both versions of iaAHCIC.inf (found in the latest ''normal'' 12.8.6.1000 version and also the latest ''enterprise'' 3.8.1.1009 version) include this line: that's responsible for the X79 C600 mass storage device. I offered you a simple solution to modify the .infs so they are integratable with Win Toolkit; if you have another, that's great. But don't expect Legolash to update his app soon, and do this by default (detect those drivers as also windows 7 compatible without other changes), as he's gone for a very long time now.

@ mooms Ok, I see. About WU Satisfy, watch out for KB2574819, it's not recommended to be integrated - generates a Win Toolkit error (RunOnce runs too early, during windows installation, and not at first boot). So please remove it from your first archive and move it to the second one (with the other non integratable updates) - will be installed before KB2592687 (RDP 8.0), so no worry. Also, about IE11, I don't think there's a need to keep a separate IE10 ''branch'', the differences between IE10 and IE11 are minor for windows 7. IE10 was a very big step from IE9, mainly because of the errors KB2670838 generated, but now nothing should go wrong. One thing I find interesting is the presence of KB2639308 in the prerequisites for the IE11 .cab (the spoiler above from ricktendo), as it's not present here. Although it's clearly superseeded (the kernel updates inside), it's currently unclear to me if it also includes some registry entries or not. Going to investigate further when I'll have the time

btw, what motherboard do you have? Normally, in the (latest version of) BIOS, there's an option to switch between the enterprise and the normal version of ''Rapid Storage'' (mass storage) driver. So normally you can use the regular one, even with the SAS port, if I remember correctly

Already done I will separate IE10 from the main packs starting today, uploading in progress. Your archive contains only security updates. I was reffering to a hotfixes arghive, that includes 400+ hotfixes for each (x86 / x64) architecture of windows 7. But glad you've post it, I'll mention it in my post / thread, so if anyone wants only the security updates, they can use your archive.

Maybe Win Toolkit detects the server word when 5.2 is present, don't know. Looked into myself and you were right. However the solution is simple - just edit the .inf and replace 5.2 with 6.1 everywhere. You can do it for any version you want or you can download the latest modded by me version from here. Verified afterwards in Win Toolkit and everything is now ok - it's a ''windows 7,8'' driver everywhere

After Patch Tuesday, probably on saturday / sunday, I'll make an archive with all the needed post-SP1 hotfixes, that are integratable, and upload it somewhere. Probably mega.co.nz is the best option, I'm open for suggestions. I'll also update it monthly, and post changelogs at mydigitallife forums only if they're considered needed. Also, I think I'll post a second archive, with unintegratable updates, that are best suited for the silent installer area in Win Toolkit. And thanks ricktendo for the IE11 cabs !!!

It may be a inf error (intel's fault). For starters, try the latest versions for your mass storage drivere. Look here.

Nope. You can get it from here. Note - it's not the original ricktendo file, I don't have it. I repacked it to make it silent, but that probably helps you

Don't get me wrong... if you add KB2592687 (and its prerequisite KB2574819) as silent installers under Win Toolkit AIO, that's ok (theoretically). I was reffering to integrating them alongside the other ~400 updates from McRip / komm 's repositories, under Updates tab in the AIO tool... And sorry for this ~ offtopic, as this is not ricktendo's fault, it's a Win Toolkit / DISM issue.

Do you want me to upload it for you? I have a mediafire account...

ricktendo has one

Something is wrong with your build. Runonce (from Win Toolkit) must run during first logon, NOT during the first install phase. I mean all the silent installers - your build has somehow been corrupted. Must likely a feature update that you've chosed to integrate, like WMF 3.0 / 4.0 or KB2592687 (and its prerequisite KB2574819). Also, I got a similar error like you, but during first logon (Win Toolkit runonce), after the install process was finished, and all I did was to move the VBC AIO installer to the end of the queue, with a y at the start of the name.

Pretty hidden if you ask me. But it works, just uninstalled on my x86 system. Please consider this optional request, to move the uninstall shortcut to the main Programs and Features location. Thanks

Great new update! I love how you made your addon not dependant on the Win Toolkit shortcut setting, and adding the shortcut in another way. Cool! Made my usual customization of this addon - only english language is preserved (1.2 MB saved - Reaper's version has 4.2 MB on the HDD, mine ''only'' 3 MB), and also it doesn't have the "Edit with NFOPad" context menu that Reaper preffered to keep in his addon. Tested on both x86 and x64 VM (my version), works great. Don't thank me, thank Reaper for a fantastic job. Reapers.NFOPad.1.67.Windows7.or.8.AddOn.Lite.WA - MD5: 96732875C9354A10AE3A45EF837F9C93 btw, Reaper, please delete my above two posts and also the post of jgp - no longer needed either of them