Legolash2o

Thanks guys :sorcerer:

Thank you

Muffy please make new topics for bugs rather than posting them in a different topic. I'm guessing you close Update catalog whilst it was downloading?

What windows are you using? Windows 8?

Fixed.

1.4.0.63^FIX: Previous form sizes now loaded correctly (maximized) If you exited a form whilst it was on maximum, it would not load correctly next time you opened that tool, it will now be maximized as previous. 1.4.0.63^FIX: All-In-One Integrator did not install LDR/QFE on XP. If you enabled LDQ/QFE in the All-In-One Integrator using Windows XP it would not install the update, this is because pkgmgr on xp does not seem to support update-bf.mum files. XP updates did not come in .msu format. 1.4.0.63^FIX: Win Toolkit now prevents users from mounting an image to the desktop itself. Some users again mounted a folder directly to the desktop itself (not a folder on the desktop), i have added some additional protection. 1.4.0.63^Update Installer disabled on XP Wouldn't of worked on XP no matter what, so might as well be disabled. 1.4.0.63^Update Retriever disabled on XP Same as above, XP did not have msu files. 1.4.0.63^Driver Installer and AIO show 'Unknown' drivers yellow instead of removing them Driver Installer now uses similar code to All-In-One Integrator, 'Unknown' drivers will remain in the list to be integrated but will be yellow. Drivers for the wrong architecture will be removed still. 1.4.0.63^Better cleanup before update integration This is just to make sure that WinToolkit cleans up all of the temp files before another update is integrated. (cInst folders in temp folder). 1.4.0.63^Made some code more simple and efficient I've replied code which took multiple lines and turned them into a lot smaller and efficient code. This will potentially remove the amount of errors due to the code being less complex.

XP isn't really supposed to have dism and Win Toolkit is not fully supported on it. 20 mins? You sure everything got integrated properly?

Nevermind, think i've fixed it anyway

I'd be grateful if you still provided the above information so i can see if i can fix it on XP

You didn't mention it within the posts, but i did just notice it under your name

Ah so you're using XP

I need: Last session Screenshot of the error Screenshot of the folder 'C:\WinToolkit\cInst_1\' take this while the error message has appeared.

English?

I seriously can't reproduce this error, i'll need your last session, screenshot of the error and also a screenshot of the folder C:\WinToolkit\cInst_1\

I never used the driverpack tool for XP. Yeah, definitely easier. I think the second phase is RunOnceEx.

Why not have a drivers folder or whatever somewhere, after first boot WinToolkit RunOnce will scan all the inf files for devices which match your computer and then next to each one th user can select install OR add and the. Processes go. Drivers have an ID which are also in the inf files so they can be used

It's fine anyway, don't worry about it

No one is marking what requests they would want to see first...

I'm not seeing 5 'unknown' drivers just 1. However 'Unknown' drivers will now appear yellow and will not be deleted. EDIT: Test 3 available.

The x64 version has 'NTamd64' in the inf file so Win Toolkit can identify it. The x86 version has nothing in it so Win Toolkit can't tell if it's x86 or x64 so it will appear as 'Unknown'

Yeah i tested x86 in the Driver Installer and still only got 1 red.

I've tried your drivers and i only get 1 red which appears to be for XP. So which are the 5 drivers that 'wrongfully appear'? http://wincert.net/leli55PK/Testing/

7z has higher compression than zip. WinRAR now also extracts 7z files too.

I just fixed an issue where if you clicked 'Save Screenshot' and then click cancel or close the window, the save screenshot button will be disabled.

oops i didn't see your original reply, check above to see any notes i've made.