RicaNeaga

You're welcome. Another thought for this default option - maybe if the C: partition has at least 25 GB free, then choose C: for the temp folder. And if it has less, then scan for another partition... This would also pre-solve the potential slowness problems. I don't know what the reason in the first place to make this option, Lego, but please reconsider it.

About the slowness issues, I think it's related to the new temp folder location via options. I tried to change the location from D:/WinToolkit (the partition that was auto-detected as having the most free space) to C:/WinToolkit, but the app has the usual behaviour to erase the folder after unmounting. So guess what: after I've run for the first time AIO, on C:, mount-integrate-unmount, and opening the app again and not detecting any temp folder on C: (the app erased it on the previous run), so the app once again had the temp folder set on D: by default. At least this behaviour is weird so the current implementation is faulty. Maybe smth like a single choice in the options to change only the partition you want for Win Toolkit to ''operate'' on, that also remains unchanged, no matter how many times you run the app. Suggestion for users with ''slowness'' issues - If you have an SSD, make (sure) the app has its folders (via options) on the SSD partition EVERY time you open the app. If you have a HDD, make sure you have those folders on the first partition - C:, the same as the original copied windows files.

Great! Also, I think you forgot about this cosmetic issue two pages back... This is also present in v68. Once again, only a cosmetic issue, but maybe you can add an exception so it won't come up yellow. Also, in v68 now I consider there is a new problem by design. I've tried in this thread to confirm that even in LDR mode the KB2685811 and KB2685813 generated explorer issues are still present, but you chose to ignore this. So please at least add a warning so users can be informed about the matter (a warning like ''even in LDR mode these two update can generate explorer issues for some hardware & software configurations"), so users may remove them from the integrating list manually.

Nope, for me these issues are also happening with LDR mode. Also, installing only 2 updates in LDR mode, and the rest in GDR mode (right now 300+ updates)... is it doable? Or if these two updates are installed in LDR mode than all 300+ updates are installed in LDR mode? Also, regarding hotfixes, please take a look at my last post in the tweaks thread. Two hotfixes currently in McRip's folder NEED a companion tweak, and also there are two hotfixes that are just tweaks. So please make that new category in AIO tweaks section, and also hope you can make those two needed tweaks to be auto-selected if the complementary hotfixes (KB2727118 and KB2732072) are added in AIO.

Please make a new category in Tweaks from AIO named Hotfixes, with the following entries: 23. KB2743013 standalone (no complementary hotfix needed) - link Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\PnP]"PollBootPartitionTimeout"=dword:0x0001D4C0[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\PnP]"PollBootPartitionTimeout"=dword:0x0001D4C0 24. KB2668751 standalone (no complementary hotfix needed) - link (FsCtlRequestTimeoutInSec from 1800s to 3600s) Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\MRxDAV\Parameters]"FsCtlRequestTimeoutInSec"=dword:00000e10[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\MRxDAV\Parameters]"FsCtlRequestTimeoutInSec"=dword:00000e10[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\WebClient\Parameters]"FileSizeLimitInBytes"=dword:1dcd6500[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\WebClient\Parameters]"FileSizeLimitInBytes"=dword:1dcd6500 Also, OPTIONAL, you have two tweaks that get added by default in Win Toolkit when two updates are added to the list - for transparency and also not to forget why they're there, can you make a sub-section to Hotfixes that just mentiones them? The two tweaks are: 25. KB2727118 Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server]"LsmServiceStartTimeout"=dword:41ffffff[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Terminal Server]"LsmServiceStartTimeout"=dword:41ffffff 26. KB2732072 Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\BITS]"BITSRealisticEstimate"=dword:00000001

Ok, after some further testing I can say for sure that at least on one hardware configuration KB2685811 and KB2685813, if installed in GDR / LDR live system, or integrated in GDR / LDR mode, generates explorer issues. So, since McRip hasn't yet decided to move these updates to an Additional folder or not, and they are still in the main folder, please include a warning when these updates are beeing integrated (AIO) or installed (Update Installer Tool) via Win Toolkit. This warning should be ideally smth like: ''This update can generate explorer issues if integrated / installed. Press YES to remove it or NO to keep it and install it via LDR mode.'' I really don't know if such an approach is very hard to implement or not, probably it would be simpler just to remove it with a warning, since it's NOT an important windows update. However, komm has a similar warning in his KUC app, and also McRip says that in some cases LDR mode is suffice to remove those issues. So the final implementation is up to you, Lego.

Yep, this may be very true. I didnt had the time to verify it thoroughly, but it seems at least some of my additional tweaks were't added to my custom image. And those problematic tweaks are... 18. Add new REG file to right click - New Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.reg\ShellNew] "NullFile"="" 19. Add new INI file to right click - New Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.ini\ShellNew] "NullFile"="" 20. Add new CMD file to right click - New Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.cmd\ShellNew] "NullFile"="" There may be also others. BTW Lego, do you think you'll have time in the near future to add some of the tweaks form their thread? This is another way of solving this issues, adding them to your app, and making sure they work.

@dareckibmw Once again, to help Lego, please name those problematic addons, maybe only those still suffer from an issue.

Most likely the new option to select the partition with the most unused space for the mount/temp folder is to blame about the slowness. If you use a SSD and a hdd most likely the temp folder will be on the HDD now in this version, and if you have only a HDD a second or third partition (etc.) will be used, again slower than the first partition (C:).

@dareckibmw Please name those problematic addons, maybe only those still suffer from this issue.

compstuff, I'm going to use tommorow v66 and give you an answer. For me v65 was issue free regarding update & SFX integration - only real problems I had with addons. So I think v66 will be ok (or maybe v67 if Lego releases another one before tommorow). BTW, Lego, was my hunch about the user-added extra-tweaks (not present in the app) not beeing integrated true? I didn't have time to check it thoroughly...

Have you tried an untouched copy of windows 7? Like the one from the links in the app (Win Toolkit). I haven't had such issues lately, even with the latest build, and I integrate 300+ updates, all green. I really dont think it's a Win Toolkit issue.

When I install both LDR and GDR (in my case) on a live system, explorer needs restarting every 5 minutes. I'm sure of it 99%, hopefully I can reach a conclusion on wednesday

Bump. Please Lego see my post from above regrading addons. None of my usual 3 addons work with build 65 - Unlocker, Whatinstartup and NFOPad. And also investigate if a suplimentary tweak that is added by the user is ok with the latest build. I can't say for sure, I just saw a tweak that I knew worked for sure in the past that maybe wasn't added by Win Toolkit. It may also be that I switched from Ultimate to Home Premium, that has less features (including Group Policy), but please, if you're also testing something else (like addons), just also add & integrate a non-present in your app tweak and test in VMWare if it was added or not.

This one isn't so urgent. Please wait a couple of days Lego as currently both komm and McRip are considering removing these updates from the main folder, and I'm still investigating if they're the cause for some weird explorer issues. So on wendsday I'll be back with hopefully a conclusion, based, of course, on my experience on a particular hardware configuration.

Yes, integrating a driver that isn't ''correctly'' digitally signed (or not signed at all) may cause BSODs. My ''fix'' was to scan manually the updatepack folder and also update them. Scan means both not digitally signed drivers and also drivers that are win7-only. It took me a few months to finally come up with something ok from my point of view. You can scan for not-digitally signed drivers with the Driver Installer Tool from Win Toolkit - install all the drivers from those folders on your live system. I'm going to make those updated drivers folders public very soon after Lego publishes a fully working version of Win Toolkit (right now it has some glitches with addons), since I want to make a final test build. If Lego is going to start working on this very important related feature, I'll also probably wait for it to be finished. If you don't have the time to scan those drivers yourself, send me a pm and I'll send you a link with mine.

Can confirm that unfortunately. Also hoping Lego will be back soon.

Great! I (!) thank you very much! Now XP only Runtime Libraries update FTW!

@jaynbe Thanks for the info and sorry for the confusion. @ricktendo I've just tried your new installer with the /ai switch twice in an x86 environment, and vc2012 isn't installed. Tried again with /ai2 switch and vc2012 finally got installed. Please update your installer to fix this /ai switch potential bug. Thanks.

See here. I don't think it's also a x64 version out there, the problems I'm having are with a x86 version of windows 7.

You can make your own silent installer from the 4.5 .net official rtm release with the ''usual'' MS .exe switches - /quiet /norestart. I can confirm it works 100% this way, as you can see with mine from here.

Details about it - here. DIRECT links from Microsoft servers - here (32 bit) and here (64 bit). Important note: you won't be able to prolongue this versions period of trial, even if you'll use an original key. For those who will buy windows in october, plese do not use this, but the RTM (yesterdays's leaked) MSDN versions.

You can try also integrating USB 3.0 drivers to boot.wim and give it a try, alongside the other chipset drivers (and AHCI/mass storage if needed), and see if it works afterwards in your case. Actually I'm very curious...

Good to have you back!

Yeah, however it's very likely that for some USB 3.0 sticks, having those drivers also integrated into boot.wim can be the little difference that permits a succesfull windows install.