Arneh

Which updates exactly? Edit: I just noticed 929399, I don't have AU enabled hence why I hadn't noticed its an exe. I'll have a look at that and see what can be done but what other update are you talking about that's also an exe?

When your Vista install is updated from WU and you get new definition updates, new updates + new Defender engine go to C:\ProgramData\Microsoft\Windows Defender\Definition Updates\ to a randomly named folder. You'll notice which folder is the latest one by Date Modified. Those 3 files then in that folder are the ones to be replaced in the Integrator in the \x86\Defender\ folder or directly in the wim in: \ProgramData\Microsoft\Windows Defender\Definition Updates\Default\ and also in \Windows\winsxs\x86_security-malware-windows-defender_31bf3856ad364e35_6.0.6000.16386_none_5585eece5b4407f1\ There's no way to download/get the updates in any other way that I know of except for through WU/AU and WSUS. Also, which updates are you talking about that are .exe?

I'm not using the MRT provided from Microsoft's Download Center if that's what you're trying to replace it with and afaik the latest version is the February one which is what I included. Perhaps the one you're trying to include doesn't have a /Q switch to it, but nevertheless I'm using the one specifically distributed via Windows Update for Vista only. I grabbed it from Software Distribution as it was updating. Also, I tried it with an unattend that also had a skipeula bit and it seemed to work fine, ie. no further updates were shown via WinUpdate for MRT. What my XML is trying to do is nothing unorthodox so if its all correct in the XML and where the MRT.exe is located, then it should work exactly as expected. I'm going to start working on a newer version hopefully later today to make it a bit more flexible however it'll probably be a week at least before I have enough time to complete it and test all the parts. The version I originally released (v0.5) was only just an early preview pack to see how it all works for other users. Edit: Just noticed the March MRT, will have a look at that later on as well.

The XML isn't too important as its just for installing the Malicious Software Removal Tool after Windows Setup which you can include in your own xml. There's no nice way to do it at the moment. About the \sources\ dir, have a look at: http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true and you'll see that \sources\ is a place for autounattend.xml as well but I think I may have made a slight mistake with that and it should be called unattend.xml since it's not a windowsPE pass and it should be in a different dir. I didn't have a chance to test the unattend part. Nevertheless, if you stick your own xml in the root of the DVD, it will over-ride it and you can delete the one in sources before or after the ISO is built if you want. In my opinion, Windows Defender updates and MRT really have no need to be integrated as they get updated all the time but they're there nevertheless.

Its because my builder was designed to update the whole untouched 32-Bit Retail image hence why there's a loop, it has to do each image in the install.wim one at a time so it will loop 7 times. As for vlite, I've tested a custom vlite version with peimg and it works however you'll have to make some changes probably to the script to make it work for a custom version, ie. get rid of loop, fix image repack name etc. Also maxXPsoft, you don't need BDD for peimg, all you need is the Servicing folder from the AIK which I included in my builder.

Never personally had that issue before and I've done an integration that involved 29 updates at one time and it went fine. Also you shouldnt have to install them one by one. Just use: peimg /install=*Package* g:\extract\windows and it'll install any Updates with the wildcard Package. Also, when you were trying to install the hotfixes, were you trying to install them on the previously built image that you made in Vista or a completely new one? If you were using the one partially made in Vista, then I suggest redoing the whole thing from XP. Also, have a look at my script, http://winbeta.org/comments.php?id=6260&catid=1 to see how I did it.

Try restarting your machine and re-trying it. Peimg integrating is a very delicate process that depends on quite a few dlls and I've had issues similar to that in an install of Vista but my method of fixing it is to boot into my 2003S install and run the tool from there and I've had no issues at all with 2003S and integrating hotfixes using peimg into a Vista install.wim. However, the Vista OS itself, when running peimg from it, may at times for unexplicable reasons have that issue though its pretty rare. And just so you know, 905866 has integrated fine for me in the past, 928089 was what gave me that error before but it integrated fine using 2003S and also worked fine after a restart of Vista, so try it again after a restart, and if you have XP/2003S installed, give it a try from there too.

"Update" have some Vista betas and Office 07 ... final Vista have Upgrade Thurrot's article in my original post *is* about the final Vista and he mentions Updates in that one while mentioning Upgrade in another. Vista 32/64 RTM or Final Retail inclune only "Upgrade" folder in root... folder include "netfx" subfolder with NETFramework 1.1 http://www.winsupersite.com/reviews/winvista_03.asp Updates folder found in the root of any Vista Setup DVD Thurrot review is from RC or beta... Check the post date at the bottom of the page and you'll see its after Vista RTM'd. "November 9, 2006" I agree there is no Updates folder in the root of the Vista RTM DVD however the upgrade folder is something completely different, its for old components as you can see with NetFX 1.1 in it. Why would new updates go into a folder called Upgrade? Or... the other explanation is Thurrot hadn't checked up on the Upgrade/Updates thing and that feature isn't supported by Vista Setup 'cause there's no documentation for it anywhere on Technet as far as I see.

"Update" have some Vista betas and Office 07 ... final Vista have Upgrade Thurrot's article in my original post *is* about the final Vista and he mentions Updates in that one while mentioning Upgrade in another.

In another article, Thurrot then says its the Updates folder (http://www.winsupersite.com/reviews/winvista_03.asp), not Upgrade. Think even he's not quite so sure and there is no documentation for this anywhere as far as I've seen.

RTM = Retail = Final = Gold = whatever else you can think of that's related so no, there's no difference between them.

Neat, to check/verify which updates have in fact been installed by integration after an install, you can go to Windows Update -> View Update History -> Installed Updates and it'll list them there.

With peimg, when one imports the hotfixes into the mounted Windows image, it hasn't installed them yet, its storing them as local cache where you don't have to download the updates from WU anymore but they will be listed as having to be installed and there is probably no dependency check in the importing phase (similar to one downloading the updates from WU but stopping the installation). I think the second part of peimg, the install phase, could best be said to be similar to one running all the msu updates manually one after another on a running Windows install, because, as its been said in other articles, offline/online servicing is identical for Vista, ie. it doesn't matter which method you use. As for the reason for two different apps, peimg and pkgmgr, your guess is as good as mine because both seem to share a lot in common.

Seeing that peimg can also be used to import hotfixes into a WinPE image which really is the same thing as a Windows Vista image except WinPE is a smaller bit/extremely light version of Windows Vista, then I would think yea, MS would probably design it so it does do some form of dependency checks though I haven't looked at that bit in detail yet.

Nice job the unknown, though you may also wanna check out http://winbeta.org/comments.php?id=6260&catid=1 which I put up earlier today which follows a similar idea to what you did and is a followup to the original article. The update pack has the msu's/UE cabs/imagex/peimg/cdimage etc. all included as well as is able to update the whole iso (all the images in the wim) and rebuild it, except I haven't tested it with 64-Bit yet, since I haven't had a chance to dl the 64-Bit hotfixes nor to install Vista x64. But yea, peimg works fine and works with vLite as well (ie. over the past few days, I've added hotfixes then removed features using vLite and installed with no issues)

That command won't make it a UDF image. It'll just make it a normal ISO with optimization. If you want UDF, add the -u2 flag to it like so: cdimage -lVISTA -bc:.\image1.bin -u2 -h -m -o .\vlite c:\vlite.iso This will make a UDF image that's in the same format as the original Vista DVD and its also worth noting that -n is not a feature that's used with UDF (-u2) images.