Legolash2o

Now that we have figured it it's x64 Recovery Mode option, i'll get right onto fixing it Thank you.

Do you get the error when it's not ticked?

Basically i just have a folder on the USB root with the drivers on (copy & paste), then use device manager to install them manually after install. If you integrate 100s of drivers into an image then: A. That will take a lot more time B. Take up a lot of space (bigger WIM, longer install, bigger ISO) C. more importantly computers will have drivers installed which are for other computers and will never get used. I have a directory in the USB root called 'Drivers' and then within that i have folders called LiamsDrivers, MumsDrivers, JimBob Drivers, ChuckNorris Drivers, etc...

I'm guessing you have x64 Recovery Mode checkbox ticked?

Hello. http://www.wincert.net/forum/forum/192-win-toolkit-guides/

buongiorno

Try the new and latest office for free. http://www.microsoft...fice/preview/en

be careful, you don't want to break any rules now

When do you get the error 'Error getting wim info'? I'm guessing you're using the AIO Disk Creator tool within Win Toolkit. does the error happen when you load your first image or 2nd image or when you click 'Create'. About the .msstyles thing, you would need to make a request in the 'Requests' sub-forum.

Mine takes about an hour and half so it depends on your system spec and if your antivirus is turned off. I only integrate into the images i use the most so never into Home Basic, the only time i integrate updates into Home basic is if i'm about to install Windows on a computer which only has that license. Again, don't do all images, just the ones you actively use. It's a shame there isn't an ISO available with all updates integrated in them already. I would host it but i don't have the space or bandwidth but most importantly i don't think that legal. Yeah, it does help having a fast computer.

I don't really use addons, i just select all x86 images and add updates then select all x64 and add updates, job done. I do use an x86/x64 AIO disk which i made using AIO Creator. Again i combine both x86 and x64 dvds so they can fit onto one disk. About making your own 'cut down' version of Windows 7, i can't really answer that as everyone has their own different needs. The only advice i can and will give it that if you know what something is (in the removal list) and you know 100% you don't need it, then tick it for removal. If you don't know or not sure of what something in the list is then keep it. But if you just want an AIO dvd then read here:

Firstly, i've taken the liberty to merge both of your double posting and please calm down If you want to know an answer to something ask a specific question. Now lets get to replying WIM AIO Creator does allow you to add the Windows 7 x64 recovery files for those computers on x64 machines, I've also managed to merge both x64 and x86 machines relatively fine into an ISO but I always install using USB anyway. I know what you mean about having everything on one single disk, it does make life a lot easier but if you have an INSANE amount of editions on one disk then most people remove things to save space which is when things can get a bit more complicated. I have never installed Start or Home Basic so I don't usually include them in an AIO. Yes Vista took a lot of resources but by SP2 it became relatively stable (for me anyway), then again I still wouldn't touch Vista with a barge pole. Same with XP but that's because it's old and out-dated. It does save a lot of time and it's perfectly save to just integrate updates and drivers as it uses Microsoft DISM application to integrate them, however removing components/features for use in something like a hospital is a big NO. Tell me more about this hospital thing. What shall I specifically add, something like "I do not take responsibility for any errors or problems which occur if you have used this program"? Give a man a fish and he shall eat for a day, teach a man to fish and he'll eat for a lifetime. Although I prefer yours. Indeed I remember you providing me with the details to add x64 recovery mode into the AIO disk, thank you. Prefer OpenOffice (free), then again I haven't used LibreOffice to really compare. Agreed, when I had to install a computer for a friend, he was very impatient and I had to leave the computer half finished because he wanted to play his shooting games. having nLite/vLite to integrate all the updates and drivers was a complete godsend, HOWEVER when it came to removing components I was VERY careful and only remove the things he would never use. If you're an IT guy wanting to re-install many machines then it's smart, more efficient and time saving to already have all of the updates + drivers installed. Personally I don't integrate drivers and just leave a Drivers folder in the USB root to make the WIM smaller and so computers don't get bloated with drivers needed for other computers. That is what Windows Server Updating Service (WSUS), this will download the updates on one machine and then distribute them to the other internal machines, saving bandwidth considerably. Again, yeah the faster it's done the better. Sometimes it is easier to use something else, although I do agree with you to some extend. If a IT guy wants to install Windows with the latest Updates then yeah Win Toolkit will get the job done and I think it's fine to start using those disks to install 'clients' computers, but I highly do NOT recommend an IT guy removing crap they don't understand and then installing that into every clients machine. So integrating updates > good, smart, efficient. Other modifications = bad. For example when integrating updates, Win Toolkit does: foreach (ListViewItem LVI in lstUpdates.Items) { Dism.exe /Image:[imagePath] /Add-package /PackagePath:[Filename] } There's more code to it than that i.e. progress bar, etc.. I don't really class it as lazy, it's a very efficient way of doing your job but again if you're an IT guy installing it on machines then I would just recommend using Win Toolkit for the update integration and not to remove features/files from the image.

Red drivers are invalid ones, for example if you selected an x64 driver with an x86 image. The cya/'blue-gray-ish' colours are duplicates, where the *.inf files have matching MD5. EDIT: I've just made some changes so that the the original MD5 remains white whilst all of the duplicates added after go to lightblue, the cyan colour has been removed.

Addon requests go here > http://www.wincert.n...equest-go-here/ I do agree that Classic Shell is a great program. However: /qr will show the installation progress but still installed automatically. Will install the start menu quietly, so you can add it to the silent installers list.

CrAzYs, that's normal and means everything worked fine. I think that update comes with SP1.

Open Win Toolkit > 'Main' tab > 'Basic' tab > All-In-One Integrator > select your WIM > Select all of the images and press select or press select > Select All > Add updates, etc.. Win Toolkit will then cycle through all of the image, making the changes you requested.

Lol i'm meant watching it on my TV

Oh, i'll give that a try now

Not really a big fan of the olympics, however i am watching the opening ceremony.

This error has been reported before and i've received logs about it quite alot, v46 adds more logging to help to determine where the problem is, i've been trying to find out what is for quite a while but i 'm having trouble reproducing the error.

Try using a clean Windows 7 image, and just have updates, see if that works.

That's the method it currently uses

Sorry i haven't been on much in the past couple of days, went home to visit my parents for 2-3 days. Also i had to take my laptop apart to clean it as it was overheating and shut itself down whilst playing Sniper Elite V2, its idle temp was 79C and under load could burn my hand. Anyways now that's cleaned it's now operating at 45C idle and 75C when playing Sniper Elite so a big improvement

When you've finished integrating you should see an 'Integrated' tab after All-In-One Integrator has finished. Also: That seems like an unattended file issue, if my memory serves me correctly.

You will have to make a request in the 'Requests' forum, it's probably better if the user extracted the files themselves as it's better in the long run and Win Toolkit would have to extract them anyway.