RicaNeaga

The extracted dvd was on my hdd. I made from it an iso on the same partition of the hdd with win toolkit. And afterwards copied the files from the mounted iso to the usb stick. So no mistakes on my end... I think

Nope, as it's already silent.

Weird then. Maybe just a one-time/run issue. Once again, sorry for insisting, please also look to the directx installer problem. Thanks again and eagerly waiting for build 53

Please look into this for build 53... maybe move by default KB943790 to the silent addons section or smth, and investigate the kb2615327 red bar issue. I'd really like a working solution after build 53 is out, so also please look to the other thread with the silent installer .exe corruption. Thanks.

Sorry for the delay, I'm more on the optimist side when it comes to aproximate time. Yes, I can confirm 100% that the Disable Mapped Drive Checking on Startup::Disable Checking tweak generates the BSOD. Sorry for not solving this earlier, but I used the old preset when testing, since the only addition to the new one was this tweak, and I couldn't believe it could be so problematic. Great however we finally know the answer.

~5 more minutes and probably I'll confirm you also... Installing...

Nope, the Disable Mapped Drive Checking on Startup::Disable Checking. Just a shoot in the dark. I'll give you the answer however in ~ 10 minutes. I don't use that 'Adjust Visual Styles' tweak.

Another weird bug this one. The fault isn't in the updates installing either. It looks like if I only install updates OR integrate addons, silent installers, tweaks etc everything is ok, but if I do all in one run then BSOD. It makes no sense. However, my last attempt is a certain tweak you added in your latest builds. If this one is not to blame then I'm going to upload the last session preset. @Mark Strelecki If you say your last working preset is ok with build 52, then maybe something you added later (a tweak or smth is to blame). Or maybe I haven't understood you, but if you have a working preset, and another one tha generates the BSOD, than maybe it would be a good idea to upload them both.

I can make it a first run update, and moving it to the silent installer folder, no problem, if it's that weird. New issue with the updates installer in AIO. I'm not going to make another thread since it's a related issue. kb2615327 x64 (ultimate x64 sp1) gives a red bar (not integrating ok) in AIO, and it's a first. I don't remeber seeing this in one of the test builds of version 51. Currently I'm using the latest build .52 final.

Microsoft Camera Codec Pack 16.4 is out. And thank you for all the updated installers from this sub-forum. I'm don't have the habbit unfortunately to give thanks more often, so this one is supposed to be a cumulative one. Thank you very much!!!

Hmmmm... I didn't verify at first if the KB943790 was really vista (6.0) only, I got ashamed when I saw you explanation, however I really don't have any KB943790 for vista on my hdd, only for 7 (6.1). You can see attached a screenshot from Everything (a cool search tool). However, Win Toolkit extracts that 6.0 version from the 6.1 .msu (???). I swear if I must that the .msu integrated is the 6.1 one from the C:\7lite\updates\x64 location, and I'm not in the renaming .msu's period. Twilight zone bug Please investigate.

For me it was Yes, to generate the screenshot.

tonight, I played with various builds to investigate that 0x67 bsod. I think I used v52 test 1 when I integrated this one, or v51 test 21 (?). I'm not sure, I deleted the earlier builds. Currently I'm only integrating updates, so I can't invstigate this one now.

Actually... no. That is the thing I found to be very weird... D4C2A66762BDA854D81C17B8707BB09E for the one on the usb stick ''iso'' (apps generated folder), and 6FE0757387C593C823F51D8C4C0FA1A8 for the one on the hdd. But the size seems to be exactly the same...

Oh... you're right. Sorry about that. My mistake. Don't know how that landed there.

I get this error when trying to add also KB943790 x64 to the update list (aside other 380 x64 updates) in the latest v52 final. ''Not compatible with 7601: 'C:\WinToolkit\CInst_Windows6.1-KB943790-x64\Windows6.0-KB943790-x64.cab' ''. I don't believe this to be true, as it's only a feature pack. Please investigate this one also, Lego. LE: added also the report log for this error. ddd.txt

Something is wrong with the first logon installer (WinToolkit Installer 4.6.3, ultimate sp1 x64). It's the first time I've encontered an issue with the directx installer - it told me it was corrupt??? I'm using it for more than a year with absolutely no problems. You can find it here... I checked the size of the one from the USB stick ''disk'' and the one on my hdd - they're the same, so the ''corrupt'' case is out of the question. Or maybe win toolkit did something to it when adding it to the apps folder? Please investigate this one Lego, it's too much for me.

About the 0x00000067 BSOD, I can confirm it has nothing to do with tweaks or addons or silent installers, but with integrating updates. So, it can be two posibilities: either something is wrong with win toolkit, either something is wrong with one or two of the updates. Currently I'm suspecting KB2685811 and KB2685813, since they're the only ones that are new additions and also can generate a driver / device related BSOD, as those two updates install the wdf from windows 8.

I'll try to investigate this one for myself a little longer, since I did many things in one run - integrate updates, tweaks, addons, silent installers etc, and since I have the time, and I'm trying to help you by identifying the exact thing that generates this error... if I can. So I'll be back later on this one. However, sorry for not opening a new thread, but it seems that build 51 final doesn't generate Vista Api.dll, and from probably many errors generated by this one I got the ISO Maker not working. Uploaded the report directly from the app. Previous test versions were fine, and I see build 52 test 1 is ok.

For me the error was the app got stuck - process not responding. I had to manually close it via task manager and re-start win toolkit.

Yes, I can also confirm this one. I found about it when trying to install some drivers, that weren't 100% digitally signed, and so they gave some errors. And taking the screenshot made Win Toolkit go bananas aka having to stop its process. Maybe the fact that I wasn't connected to the internet had something to do with this one.

Yes, I'm also getting this from yesterday, I was using version 51 (test versions), I'm in the process of finding out the cause. I'll be back when I''ll have the answer.

Huh? Weird then. I like it however with the line for those. Just my 2 eurocents.

It's ok now. Although there's a thinner line with the same unwanted effect for the top tabs (Welcome, Main, Tools,Downloads or About tabs, and Main, Intermediate and Advanced sub-tabs, but only when they're not opened), I like that the current opened tabs doesn't have it, the same as the buttons. So having that line for the not opened tabs makes them stick out a little, actually a very ''wantable'' feature I think for a person that comes for the first time in contact with Win Toolkit. So my vote it's for the current look in test 12. I don't know if you've left them knowing it, but those lines for the un-opened tabs is just ok. Probably without them the interface would be more dull / too simplistic / too clean for my taste.

I like it more now - the design I mean. However, that line in the buttons is still there. And if the user has a dark background, the high transparency is still making those buttons look ugly. Once this issue is fixed, it's pretty final to me. v51 FTW!