compstuff

I'm confused... what new release?

IMHO that's exactly why I suggest people do this in steps...how do you know where the problem is? Is it with the hotfixes? Is it with the removals? Is it with the tweaks? If you had created an image with the hotfixes and that worked then you could keep that WIM and just play with that adding tweaks, removals etc until it works... much easier that having to run the entire process over from scratch.

Great news :dribble:

I am extremely interested and was going to request this... thanks

I wondered... that's awesome thanks

Rick, does this installer auto run Ngen tasks?

I had also seen that a few times when I was starting my USB installs on some Dell laptops BUT mine was USB 2 drives with USB 3 ports... I haven't seen that problem in ages though so I can't provide any useful info

I just tested it and etz is 100% accurate... I used some time stamping to determine what runs first and sure enough... now I have to figure what if any impact this has on my process Here is some basic info about the timing: 1049 setup is starting copying windows files1058 1st reboot starting windows, updating registry1059 starting services, flashes, completing 1st part gui install1104 setup will continue after restart1104 2nd reboot starting windows1105 preparing 1st use, video check,1105 SETUPCOMPLETE.CMD 1106 welcome, preparing desktop1108 sfx #4 of 481132 kommclean1133 personalize settings screen Done

I am running a test now

That's a nice find :-)

I use this tool on all my integration's files before I do them: http://www.nirsoft.net/utils/alternate_data_streams.html

I definitely don't know why you are having this odd problem but here are some further comments: I have never been able to get the MS WIN7 USB tool to work with anything over a 4 gig stick I never used the WinToolKit USB tool so I have no experience with it, I have been using Rufus http://rufus.akeo.ie/ I have never used a USB 3 stick but I can't see why it would be a problem since you are on a USB 2 system Maybe try Rufus and see if it changes the problem in anyway or maybe reformat the USB and start fresh again

I never knew about the GUI so you turned me on to that one... thanks :-)

I will PM you :dizzy:

Since I am not on XP I could be wrong... but I think they do actually get installed its just that XP doesn't have the capable service to make use of them and it never will

This explains it better than I can :-) http://www.windowsecurity.com/articles-tutorials/intrusion_detection/Network-Inspection-System-Enhances-Security-Microsoft-Security-Essentials-TMG-Firewall.html

http://www.alexlomas.com/blog/2005/08/64_bit_wget_for_windows/

How exactly are you making the USB with the ISO

I have never been able to find one with the x64 designation and I used to just rename mine with my script

I have a whole bunch of stuff I add to my image and I include an automated install of Office 2010 with it so I'm running about 10 gig right now and I use a 16 gig USB

There is an x86 and x64 version: http://www.microsoft.com/security/portal/definitions/howtomse.aspx Network Inspection System definitions: http://go.microsoft.com/fwlink/?LinkID=187316&arch=x86 http://go.microsoft.com/fwlink/?LinkID=187316&arch=x64

Question; can your package also add the nis_full.exe file as well? FYI I use the following to quickly update my existing method and will now use it for yours wget64.exe go.microsoft.com/fwlink/?LinkID=121721&arch=x64 wget64.exe go.microsoft.com/fwlink/?linkid=207870 wget64.exe download.microsoft.com/download/DefinitionUpdates/mpam-fex64.exe

That is one of the best tools and I use it often... I also use Windows built in C:\Windows\System32\iexpress.exe

I don't have specific answers for you but have you considered using USB for installs instead of DVD? I no longer burn DVD's and I love how fast the USB installs are.

Glad it could be of some use... I have been delayed in making my next update because I too have been refining my methods to make some improvements. Ironically they happen to be in Step-2 and Step-3 (driver Integration) and were prompted by the posts that have occurred over the last 2 weeks or so.