Legolash2o

Thanks, i will fix it once I get home from work. (5 hours time)

Expect a new release today

Expect a new release today

Try this if you it won't unmount:
 
 
 
Dism /Remount-Wim /MountDir:<path_to_mount_directory> Then try unmounting again via WIM Manager

I've finally manged to replicate this issue, I had to restart my computer and manually unmount the image. I will fix it after further testing

I'm still doing code refactoring, investigating bugs and also reading a programming book

I've finally manged to replicate this issue, I had to restart my computer and manually unmount the image. I will fix it after further testing

I'm still here.

This will let you have you Windows installed unattended. It's not the most complete unattended out there but it's better than nothing.

Luckily most of this is self-explanatory, note it is recommended to leave 'Architecture' set to 'AnyCPU' which means it should work for both x64 and x86 installs.
Main
This is where you select the most important parts of the unattended file, like your name, serial key, time zone, screen resolution, updates, Auto-Logon, etc...
Users
The 'Users' tab lets your add pre-installed usernames on the computer, with passwords, user group, description, again self-explanatory.
Editor (Advanced)
It is recommended to leave this alone unless you know what you're doing, since W7T does not have full unattended features it allows users to add their own entries and save them to a file, it also allows the user to see what will be saved.
Serial Keys
These serial keys are known as 'Default Keys', they are basically just used to make the install unattended by leave Windows de-activated and keeps the 30 day trial.
WARNING: If you use a Ultimate serial key then you must install Ultimate otherwise it will error.
Integration
You can use the 'WIM Manager' to integrate a unattended file.

Also available via W7T!
51.1MB
63C1B8255EAC9C74B52206A669D366E4
Description
"Windows 7 E" does not come with a web browser, when you integrate this it will popup after install to let you choose what browser you want! Just in case the browser you want is not listed, it also includes a small built-in browser so you can download it yourself
Note:
You can still use this even if you do not have the E version!

The Language Pack Converter tool converts your langauge packs from the .EXE form to the .CAB form so you can use them to integrate into your Windows image, using either the All-In-One Tool or another program from a different developer.

Step 1: Add the Langauge Pack(s)
Click the Add button, browse for your language packs.exe
Step 2: Starting the process
Press the Start button and select the folder you want the .cab to go
Step 3: Wait
Items that go Green mean they have converted successfully, that's pretty much it.

I would add 2013, but I can't find the PM you sent me with the details. A lot of users tend to message me rather than write in the forum about their issues. So naturally I get lots of messages.

This will let you have you Windows installed unattended. It's not the most complete unattended out there but it's better than nothing.

Luckily most of this is self-explanatory, note it is recommended to leave 'Architecture' set to 'AnyCPU' which means it should work for both x64 and x86 installs.
Main
This is where you select the most important parts of the unattended file, like your name, serial key, time zone, screen resolution, updates, Auto-Logon, etc...
Users
The 'Users' tab lets your add pre-installed usernames on the computer, with passwords, user group, description, again self-explanatory.
Editor (Advanced)
It is recommended to leave this alone unless you know what you're doing, since W7T does not have full unattended features it allows users to add their own entries and save them to a file, it also allows the user to see what will be saved.
Serial Keys
These serial keys are known as 'Default Keys', they are basically just used to make the install unattended by leave Windows de-activated and keeps the 30 day trial.
WARNING: If you use a Ultimate serial key then you must install Ultimate otherwise it will error.
Integration
You can use the 'WIM Manager' to integrate a unattended file.

New test version is out: http://wincert.net/leli55PK/Testing/

New test version is out: http://wincert.net/leli55PK/Testing/

Before I talk about long term plans, I will talk about the next release. v1.4.1.12 already has a few bug fixes and enhancements.

Short Term - Next release:

*1.4.1.12^FIX: "KB2670838" will always be integrated before IE10. Because it is required for IE10 to be integrated.

*1.4.1.12^FIX: Typo on new 'Windows ISO' screen. Nothing special.

*1.4.1.12^New method of detecting update integration. Usually updates go green fine but some stay red. This new method gets the package name which you can see when you put your mouse over item. Anyways, all updates should now go green unless it's for the wrong version of Windows. For example, Windows 2012 updates won't integrate into Windows 8 and will show red.

*1.4.1.12^KB2764913 and KB2764916 (IE10 files) can now be integrated on x64. Any processor architecture neutral updates can now be integrated.
 
*1.4.1.12^'Windows ISO' > 'Exclusive ISOs' now displays download speed and time remaining.

I won't release v1.4.1.12 yet as I will be going through the automated error logs to fix what I can.

Long Term:
I'm still very behind with the code refactoring so I will have to dedicate at least an hour a day to get the job done. I haven't really done much recently and it really needs to get done before I can add new features. I will of course keep you guys updated on its progress

In case you've forgotten, code refactoring is where you replace older and possibly more complex code with newly learnt and simpler code. This helps create an efficient, simple and more streamlined program but also helps me squash bugs.

Also Win Toolkit production may end (except bugs) when Windows 9 comes out but I will start a new tool dedicated for Windows 9

Anyways, back on point. When the code refactoring is completed I will finally be cycling throw ALL the request topics for the v1.5.0 release. I really need to get the code refactoring done first.

Releases:
Sometimes I can get carried away with release and release multiple updates a day, this tends to annoy people and therefore I am thinking about trying to release a beta build every night (assuming if anything has changed) and a public build every Sunday night.

This will also allow me to gather enough log data to release bugs and give you guys a chance to report more errors. The only time I will release an update before then is if there is a massive bug which needs to be addressed.

Automation:
I'm trying to make more processes in Win Toolkit automated for me. For example, the new update integration check will make life a lot more simpler for every body as you should no longer receive red updates.

Error logging is already fully automated which is brilliant as most users don't report bugs at all. There are, however, more things which could be automated for me which will give me more time for programming.

I will try and make donations more automated so users don't have to wait for me to give them a key.

Oh i haven't put it in WIn Toolkit (yet), i was just testing the idea out manually and it works great

I've just used this method and it works nicely

DISM probably had a whole team of people to create it, i suppose I could monitor an integration and see how it works fully.

My SSD is 'Out-for-delivery' and i've already started to prepare my Windows 8 disk ready for installation. I can't believe Windows 8 already has like 61 updates already :/

My SSD has arrived but I'm still waiting for WinToolkit it finish integrating updates/drivers. It's a lot slower when using a HDD

No point having better hardware as my SSD is at the SATA II limit anyway

Now, that's good time for a disk to fail

Luckily I'm still within its 3 year warranty by 2 weeks haha.

Since we moved to datacenter in Germany, server is working flawlessly.