gotenks98

Just wanted to check if dism is windows 7 only or not. I been trying to integrate updates and hotfixes for vista sp2 wim file but it always gives me the 0x2 error when I try. I am doing the package path switch with the .msu files. I have tried with just cab files and still it does not work. Just wanted to know is there some limitation on this or do I have to find an older version of the waik to do sp2 images?

@gotenks98: Can you advise how to turn off system restore in "Autounattend.xml"? Or, turn it off using a registry tweak just before running "setupcomplete.cmd"? Thank you! amd64_Microsoft-Windows-SystemRestore-Main on the Waik

I would slipstream the updates using the waik. There are a few that can not be though. Those are the .net 4.0 stuff and the like 1 or 2 regular updates. .Net 3.0 stuff can be slipstreamed just fine. I would not slipstream IE9 though, it has an odd bug that will always open the welcome wizard every single IE run. Although you can use registry fixes to stop it I would rather not as I do not know if that will end up breaking something in the future. As for as doing the setup complete for each update thats going to take a year and a day to run unless you specify system restore is turned off during the unattended install. With system restore on it wants to create a restore point for every single update which is a waste of time and disk space. So in short slipstream what you can and what you cant just put in setupcomplete. I am more interested in getting the firstlogoncommands thing to work. So far I havent found a sure fire method that makes this work on a 64-bit setup.

Lol, no thats not the issue, I just have sticky board which is why the A does not show up in that post. Believe me that was the very first thing I checked for. I got it to see my answer file now. I just totally recreated it from scratch not sure why it works now.

I got it working for the cmd to stay open but it does not show any text for it. Still trying to figure this part out. I will post back when I get closer to working it out.

You have to make a folder in your sources directory, it does not go in install.wim. Its sources\$oem$\$$\setup\scripts

Right now I have only tested this recently in virtual box. I wanted to know before I started using vm player if this is just a issue with vm's not reading answer files. I would use virtual pc but it does not support 64-bit guests. I would love to get this working in virtual box because the options are alot easier to configure. Vm ware is horrid in that aspect because its really hard to get into the bios of the vm to make adjustments.

Just want to ask is there some kind of trick to get the autounttend.xml file to read in virtual box or other vms? I have been trying for a week now and still can not get this to read at startup. I know I could get it to work with it if I did the setup /unattend: command but I want to run it at the start of setup from boot. THis will be for testing the xml file from a dvd or usb for windows setup with no OS. I have tried about 20 ISOs, I have tried putting in the root folder, in the sources folder and in the boot.wim file on the 2nd index. Still it ignores my xml file. I have even tried one of the known working xml files listed on the forums and it still does not read. I tried using a virtual floppy in virtual box and it still does not read. I even got virtual box use my usb flash drive with the file redirect and still does not read. I have even tried using both x86 and amd64 entries and still not reading. I am at a loss at this point.

So what in the code keeps the dos box open or open a new one? My problem is I dont see the dos box at all when this is going on. Most of my code I got from various websites. I totally suck at programming which is why this is so hard for me.

Tried that I dont see a dos box at all when this thing is going. Not sure what I am doing wrong here.

Ok so I think I kind of got this working now using the following code @echo off setlocal enableextensions disabledelayedexpansion (set CDROM=) for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do (if exist %%i:\sources\install.wim set "CDROM=%%i:") if not defined CDROM goto :eof start /wait %CDROM%\Updates\IE9-Windows7-x64-enu.exe /passive /norestart /update-no start /wait wusa.exe %CDROM%\Updates\AMD64-all-ie9-windows6.1-kb2530548-x64.msu /quiet /norestart /nobackup start /wait wusa.exe %CDROM%\Updates\AMD64-all-ie9-windows6.1-kb2559049-x64.msu /quiet /nobackup /norestart start /wait wusa.exe %CDROM%\Updates\AMD64-all-windows6.1-kb2533552.msu /quiet /norestart /nobackup start /wait %CDROM%\Updates\AMD64_X86-all-silverlight.exe /q del %0 What I need now is some way of knowing what its doing right now. Some sort of progress bar. For some of the apps it does like IE9 but not the windows updates. Back with windows xp the /passive command would do this but that does not work with updates for vista going forward unless its a service pack. Any ideas how to create a progress bar of some sort that can go for each app?

How do I set this up to use that?

I think I got that part fixed. I just cant get order 1 to run. I get no indication that its running, nor do I see any of the others once the paths are fixed. This is turning out to be harder than I initially thought. For the for loop part which phase of the unattended file does it need to be? Like specialize or oobe? This is the updated code for the order 1 in specialize pass cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\Autounattend.xml SETX InstallDrive %i:\ -m" This is for order 1 in Oobe pass cmd /c %InstallDrive%\Updates\IE9-Windows7-x64-enu.exe /passive /norestart /update-no This is the code for order 2 cmd /c wusa.exe %InstallDrive%\Updates\AMD64-all-ie9-windows6.1-kb2530548-x64.msu /quiet /norestart /nobackup This is for order 3 cmd /c wusa.exe %InstallDrive%\Updates\AMD64-all-ie9-windows6.1-kb2559049-x64.msu /quiet /nobackup /norestart This is for order 4 cmd /c wusa.exe %InstallDrive%\Updates\AMD64-all-windows6.1-kb2533552.msu /quiet /norestart /nobackup This is for order 5 cmd /c %InstallDrive%\Updates\AMD64_X86-all-silverlight.exe /q

Ok I think I got it started but it wont launch. It does nothing at first log on. Here is my xml <?xml version="1.0" encoding="UTF-8"?> -<unattend xmlns="urn:schemas-microsoft-com:unattend"> -<settings pass="oobeSystem"> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup"> - <FirstLogonCommands> -<SynchronousCommand wcm:action="add"> <Order>2</Order> <CommandLine>IE9-Windows7-x64-enu.exe /passive /norestart /update-no</CommandLine> <Description>%InstallDrive%\Updates\Internet Explorer 9</Description> </SynchronousCommand> -<SynchronousCommand wcm:action="add"> <Order>3</Order> <CommandLine>wusa.exe %InstallDrive%\Updates\AMD64-all-ie9-windows6.1-kb2530548-x64.msu /quiet /norestart /nobackup</CommandLine> <Description>IE9 Update kb2530548</Description> </SynchronousCommand> -<SynchronousCommand wcm:action="add"> <Order>4</Order> <CommandLine>wusa.exe %InstallDrive%\Updates\AMD64-all-ie9-windows6.1-kb2559049-x64.msu /quiet /nobackup /norestart</CommandLine> <Description>IE9 Update kb2530549</Description> </SynchronousCommand> -<SynchronousCommand wcm:action="add"> <Order>5</Order> <CommandLine>wusa.exe %InstallDrive%\Updates\AMD64-all-windows6.1-kb2533552.msu /quiet /norestart /nobackup</CommandLine> <Description>KB2533552</Description> </SynchronousCommand> -<SynchronousCommand wcm:action="add"> <Order>6</Order> <CommandLine>%InstallDrive%\Updates\AMD64_X86-all-silverlight.exe /q</CommandLine> <Description>Silverlight</Description> </SynchronousCommand> -<SynchronousCommand wcm:action="add"> <Order>1</Order> <Description>Setup Media Drive</Description> <CommandLine>cmd /c FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\Autounattend.xml SETX InstallDrive %%i:\ -m</CommandLine> </SynchronousCommand> </FirstLogonCommands> </component> </settings> </unattend>

I am trying to make a fully functional installation disc for just windows update for windows home premium. The reason I am making this disc is for my dad who is very computer challenged so using 3rd party apps to make this work is out of the question due to him possibly screwing it up some how. What I want is to slipstream as many of the updates as I can and whats left over can install at first log on. I already got the drivers down pack so thats no issue there its just getting the updates and maybe a few things like java and adobe reader to run at first log on. Any idea how to do this using autounattend.xml file? I been looking over many different threads but its kind of hard to make sense out of some of the code that is written for the loops. Basically I need to know how to do this and what each part does so I can understand why the code is written this way. Small Edit: Also I want to make this so it can install from dvd and or usb.

for those of you who wrote scripts can you tell e exactly what the code is doing so I get an idea as to what to expect. Also how would I get this to run from dvd or usb? I have had the worst time trying to get anything to install from dvd or usb using answer files. Any help or guide would be appreciated.

Sorry for the lat reply to this thread I got a few questions. Whats the difference between using the exe version vs. using the msu version? I am having problems with the ie9 always wanting to run the welcome screen on every run of IE. I saw online there were registry hacks for this but I do not want to go that route I want to ensure this is actually installing correctly. Right now I have an image that I want to put into a production environment but this bug is why I am holding it back.

I am trying to integrate IE9 using the Waik via the DISM but I am having one problem I just cant stop. Every single time I open IE9 it wants to run the welcome screen. While know this can be disabled via group policy or registry hacks, I just want to get to the bottom of whats causing it in the first place so I do not have to have this problem. Any ideas on this? I know that if I apply IE9 via MDT I do not have this problem.

I am getting the following error in virtual box. "Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valide, and restart the installation." This is when i do the $WinPEDriver$ thing. Nevermind, I think its bad driver files. I removed a folder and it got past that step. But now for some reason its refering to wim file thats not even associated with this install.going to start it over. I guess I need a way for it to not even look for a wim file.

This is exactly what I am looking for. I just got a question how do you test this in a vm to see if it pulls in only certain drivers? Also can this be done for windows updates? Normally I would slipstream but it just takes too long and this method would really help on saving me alot of time. Small Edit: Does anyone know if its possible to have multiple versions of windows 7 or vista to use the same autounattend? I know 32 and 64 probably couldnt but what about say havine one file that will work for ultimate and professional?

Basically what I am trying now is to have windows pull drivers from a store on a usb drive. We have a few systems that can not be put on the network due to research privacy issues. What I would normally do is have the drivers come from the network during a normal windows install but how would you do this if you wanted to drivers to come from a usb drive in which you are installing windows. Normally I would just slipstream it but this would be a ton of drivers creating driver bloat. In another post I asked few weeks back I asked on how to reduce or eliminate the bloat. I think I found a way around that but I am not sure how to set it up from the local drive instead of the network. I remember a long time ago with vista this was possible using some kind of cd rom environmental variable but I just can not find the documentation on this again.

Also I wanted to add I got a partial resolution to this problem already. Not the best solution but after hours of googling I found out that there are others who have had this same problem and the only way to get past it was to use a SP2 disc that is manually slipstreamed to SP3. Once slipstreamed it works just fine on installing. Pretty much all the SP3 discs from dell have this same issue. I would have liked to been able to use the SP3 disc but I am running out of time for this project.

Yep, but IMHO that says that the feature/specific use/scenarios of the program are not supported (which does not necessarily mean that it is "illegal" or "a breach of license" or "an actual crime"). AFAICU what the MS keyb says is layman's terms : jaclaz Exactly what I see when I read this. Again which is why we have forums for this kind of stuff. If you really want to get techical on it then they could say the same thing about stuff like nlite, vlite and all the other slipstreamers out there but yet there is support for that stuff here.

All that says is that its not supported. It doesnt say you cant do it. Thats two completely different things. As I said before many of you are grasping at straws here just trying to be the software police. Seriously how often does microsoft actually call people up over minor stuff like this? I could see if it was someone saying they were going to install volumn license media illegally or something on non-company owned machines. This is just a simple rebuild to get past the pre-installed junk on the systems. If worst comes to worst we will just get a system builder license if we have to just to get this done so we can have more control over the installation.

Ok then explain to me why they have an express deployment tool just for OEMs then? http://www.microsoft.com/OEM/en/downloads/Pages/ExpressDeploymentTool.aspx Thats one thing I saw when searching for an answer to the original problem. Thats right there says they do not care about mass imaging because the tool is specifically designed for that. Not to be rude but it seems like you guys are trying way too hard to be the software police around here.