Legolash2o

The latest build is in my signature and already available.

I've managed to hopefully fix all the RunOnce issues with the latest test build 1.4.37.2. You dont have to start the process all over again, you just have to mount the image > unmount + save and you will have the new RunOnce. The link to the latest build can be found in my signature. Other fixes include: *1.4.37.1^FIX: Fixed updates issue with RunOnce *1.4.37.2^FIX: Fixed adding IE and XP Mode to AIO Updates*1.4.37.2^FIX: Minor fix to Alpahwaves Downloader*1.4.37.2^FIX: Minor fix to Update Retriever

Oh forgot about this issue! I've bookmarked this to fix this definitely by tonight (UK time).

@Cartman, I will continue this discussion in your other thread. http://www.wincert.net/forum/topic/12100-wintoolkit-14371-silent-installer-dosent-work-i-have-try-with-x86-x64/ @Everyone else Well i've uploaded a new test build, please give that a go @Emoreg Latest test build fixes that.

Do you mean it can't be added to the list? EDIT: Confirmed issue. I will fix it right now!

Confirmed. Investigating it now. EDIT: I manually entered the URL and apparently it no longer available: I don't have control over the lists so I can't remove it.

Just fixed the msu, was a stupid typo on my end. I was passing C:\...\1.msu" instead of "C:\...\1.msu" (quote missing). P.S. Windows updates should be on their own tab anyway so that another bug. UPDATE: Uploaded test version.

Please re-download v1.4.36.1 if you have already downloaded it before I posted this. Finally fixed an issue with the runonce, sorry for any inconvenience. UPDATE: GRRRRRRRRRRRRRRRRRRRRRRR, I've just had to release 1.4.36.2 to fix a bug which shouldn't have need to be fixed. Basically, visual studio told me to try something when it analysed my code and it actually screwed that part up. So i've just undone it. Again, sorry for any inconvenience. I won't release anymore this weekend. Just test builds.

Found the issue once and for all. Will upload now SharkCodec doesn't even install silently even when ran manually with switches. Neither does USB/DVD tool UPDATE: Go to the main download page and re-download v 1.4.36.1b

Already fixed in v1.4.36.1

It searches a bunch of pre-defined locations and your custom folder. I then believe it will use the latest version it finds.

With Windows 7 you provide the key after Windows Installation if you need. Just make sure to select the right version the key is for.

Are you using install.ini or AIO Integrator? Is it EXE or MSI files? UPDATE: Nevermind, it's EXE and just fixed it

Download an ISO via Win Toolkit then following the following link: https://www.sctxca.org/suncity/clubs-groups/sites/computer/sigs/win7/articles/Win7_Retail-to-OEM.htm In the sources folder open ei.cfg with notepad Change retail to OEM: I'm pretty sure you can just delete the ei.cfg either way You made need to change 'Ultimate' to 'HomeBasic', 'HomePremium' or whatever version you have.

Following on from the first report. In decided to rewrite the entire error logging system due to many problems with the old version. Here are some of the new benefits: Each type of error has their own unique ID so that they are group together and easier to manageLogs can now contain foreign characters so most of the non-english computers have the most issues.You get a balloon popup when a log has been saved and uploaded. Which you can click to view.Shows the user much more error information. The exception errors are in the users' own language.Much simpler and easier to manage code.Different types of errors which help prioritize errorsBefore I describe what stage 2 is. I will give details of the types of messages. Large ErrorsLarge errors are the ones you will hopefully not see. This are the boxes which give you the option to view more details and the entire exception information. Small ErrorsThese don't produce an error box, they just upload straight to the server. Mostly used in integration so that the process doesn't pause and wait for the user to click OK. Unhandled ExceptionsBasically anything I haven't put in a Try-Catch statement. These are the big ones which I usually try and fix ASAP. Test ErrorThese are for me and just uploads an example test log to the server for me to check if it's working. Click here to view a log file sample. Legacy ErrorsThese are the errors which still use the old code. Although they use the latest code to save and upload (to support foreign characters). They are unfortunately crap in regards to detail. This is where stage 2 comes in. Stage 2: Stage to is to manually go update all the calls to the old writelog method and update it to the new one. These will take a while Moving onto the new system will allow you to view as much information as possible in a neat format whilst allow me to fix bugs

Sorry guys. I had to delete ALL but 3 personal messages as my inbox got full If you have sent an important message which still requires a reply, feel free to resend the message. However, please remember bugs should go in the bugs sub-forum and that general questions should go onto the forum.

Thanks I will test when I get home. Just before I left I've implemented which will show why drivers haven't been added and an option disable it from automatically removing invalid drivers.

Anywhere you can online and just a small handful. If less than 2MB 7zipped up, then just attach it to your next post

Sorry for lots of releases in the past few days. I'm still receiving big issues on the old system which I've moved over to the new system in the latest release. This will allow me to find them once and for all. I've also fixed a few important bugs with the RunOnce tool so it was worth it. I'm currently tracking a really nasty bug which about 90% of the error logs I receive so it was really important that I move it over to the new system. I've also made it so that the 'Details' button on the error box shows you ALL the information it has collected rather than just a few bits and bobs of useless crap.

Thanks, much appreciated. I've already uploaded a new test version removing the console window and other fixes to the main Win Toolkit exe.

I can fix that, make sure you dont have it in both install.ini and registry. You may have integrated a few times into the same image

Maybe upload a few drivers?

The only thing I can imagine causing that is that the Drivers folder either has no *.inf files in it or that they are all x86 drivers.

Fixed, in the latest test build

Oh damn, you're right! I think it's adding it onto everything! EDIT: IT adding it to everything you add via AIO-Integrator but not install.ini, fixing it now!