As you talking about Latest Hardware most of them cant be able to install XP (clearly i cant confirm because i stopped using XP after Windows 7) even then it is better to Installing Operating System from USB is nice for that situations. You can easily modify(update) the files when ever you want.
You said you had removed a lot of legacy drivers. Actually, I wish to remove many legacy drivers as well: "Cameras and Camcorders", "IBM PS/2 TrackPoint", "IBM ThinkPad", "Logitech Wingman", "Microsoft SideWinder", "Printers" (nLite suggests to keep just a specific file needed for PDF printers, do you know its name?), "Scanners", "Sony Jog Dial", "Toshiba DVD decoder card". Do you have a similar list of removed drivers?
Winlite Iso File Download 72 Mb
If you want to know which specific printer drivers I removed please send me a PM. If I load my current Windows XP Source in nLite I can still select Printers to remove as an option, file size 33.74 MB.
I think you should be fine using these latest packs. If you use these you don't need to add DriverPacks CPU, as these are now part of DriverPack Chipset. Ignore the warning about the missing Driver Pack when using DriverPack Base.I think you should look at your current modem connection. In almost any case the dialup modems in newer laptops are using the default Windows XP dialup modem driver. In very rare cases the manufacturer would probably have included a cd with modem drivers. These would probably be much newer than the ones from 2001.When removing the Modem drivers using nLite it will keep the default driver for compatibility.The only issue I ran into was about part of the Nokia Modem connection not working correctly without mdmcpq.inf.You only need to add this file to the nLite exclusion list and you should be fine removing all the modem drivers. They take up a lot of space and slow down Windows XP setup.You asked about removing the default printer drivers. These take up a lot of space. If you want to keep PDF printer support you have to add the files to the nLite exception list when removing the Printer Drivers.You should run nLite multiple times, as removing components and integrating addons in the same run is asking for trouble.The Ricktendo and YumeYao common printer driver pack contain the latest printer drivers. Probably your new printer also requires these files.Most of the files included in this pack update the same files as on the exception list.It will only increase the size of your I386 slightly, but it is still a lot smaller than when you keep all legacy printer drivers.About ISDN. I would still check if any of the ISPs on Malta have implemented ISDN connections. You probably don't need it.
Do not confuse this manual directory delete process with the Manual Install and Upgrade option offered by nLite. Using the Nlite option will remove winnt32.exe and additional setup files as well, not only removing upgrade support but also the ability to install the recovery console. If you don't want to install the recovery console ever you can select this option to save some space, but I do not recommend it.
I have not tested nLite if it supports updating uncompressed svcpack.inf. I remember it did process these files, but recompresses them again. This makes it hard to compare changes when using version control.
While the extent of the performance increase is going to vary from program to program, the drive itself is extremely fast. When copying a .iso file to the Radeon RAMDisk, it was limited by my SSD's read speed, for example.
In addition to the file copy tests, I also used the HDTune benchmark to measure transfer speeds. Needless to say, RAM blows solid state NAND out of the water in speed (though it does cost more and is volatile storage).
Over the years, I have used a RAMDisk for hosting photo editors as as using the drive for media I was currently working on. It worked well at the time, but the free software was not exactly what I would call stable. However, the AMD software is a mere 6.2 MB download that installs quickly and is easy to configure. The UI is spartan (and resembles Windows Classic), but it gets the job done and has yet to crash on me after trying to break it today (heh). It does not feel "janky" at all, and I have to give AMD and Dataram props for that.
PS there is another limitation, if the RAM disk uses only 1 CPU core then you will be limited at around 6GB regardless of how much you overclock the NB and memory clock speed. RAm disks can easily max out a single core if you are transfering a large file.
Note that these update lists will be the final version as they include the last patches released by Microsoft before the end of support (any bugs or errors will be fixed). Optional update KB4493132 might be offered for download during an update check. This is the Windows 7 end of support popup nag which is not required. Just ignore or hide the update.
These lists do not contain all available Microsoft patches but those that will bring a standard system up to date in accordance with Windows Update. One exception is the definitions for Windows Defender. Double click the downloaded ULZ file to import the list to the WUD program.
7. Click the Apply button, check the Create ISO box and choose the save location and file name for the ISO image file. Press the green Process button and wait for the integration to finish.
With a check of Windows Update, you can see we only have a few updates left, Some of them can be removed by adding optional updates like .NET and the MSRT. That would leave us with only Windows Defender definitions. Do be aware that you still might have hardware drivers and any other updates which are region or language specific to download, but the vast majority are now already installed.
1. Download our EOSNotify_Del.bat file. During the Windows final setup phase, it will rename the EOSNotify.exe that installs to System32 and remove the two scheduled tasks that run the executable at certain trigger points.
Hi, i saw other website integrate all updated windows 7 with the esd compression, so after integrated the iso only around 3gb, but i wonder how they do, only know it using dism tools.i try myself using nlite at the last step choosing esd compression, but the iso created cannot use for install windows 7, it comes out the error image file install.wim does not exist.
I have followed the instructions given and when trying to run the install it gets to the second part of the process expanding windows files at 1 percent and fails to install stating that the install could not be completed as it is missing important installation files with error code 0x80070083. I am attempting to add all updates including the optional software included in the updates. is there something I am missing
The ULZ files can be edited if you know which updates are language specific (I have no idea, to be honest). It probably would be easier just to download them and then add them to NTLite manually instead of changing the ULZ files.
The ULZ file is only a Zip archive, so just rename to .ZIP and extract it with Windows or directly extract it with another archiver. Inside is a UL file that is a plain XML text file you can edit with Notepad etc.
Open up your ISO and look in Sources > $OEM$ > $$ > Setup > updates (if that path is available). You will likely have a few updates in there. Get some ISO editing software and rename or delete those files (and anything else in there) as they will be the ones installing during the finalizing settings phase. Then try again.
I had all the files on a NVMe SSD, so the integration only took 30-45 minutes. The resulting USB drive contents total out to 3.34 GB as reported in Explorer. I made sure to select Win7 Pro x64 in NTLite.
Steps:1. Download WAIK and mount/open the iso file.2. In Neutral.cab, you will find F1_imagex, F2_imagex and F3_imagex. They are the x86, IA64 and x64 versions, respectively. Extract the appropriate one (most likely f3_imagex) and rename it to imagex.exe.3. Use imagex to split install.wim into install.swm and install2.swm (with appropriate paths to files)imagex /split install.wim install.swm 3800(the number indicates the maximum size)4. Replace sources\install.wim with the swm files in the Win7 iso or the FAT32 partition.
Thanks you for your article, i was trying to follow your guide using windows 10 to make an iso of windows 7 but forced to use Windows Hotfix Downloader because unable to install WUD on windows 10.Can you tell me how i can put your download list for UWD in WHD?As you wrote, WHD list too many hotfix to dowload, es. why download ie10 if there is ie11.
Hi. Thanks for this useful tutorials, i did follow every step. After installation my newly fresh Windows 7 x64, my windows update shows up only 100+ files need to download and i noticed that 20 files that i already slipstreamed is still on the list. Do i need to download those or ignore it. thanks !
It worked that simple, EXCEPT for IE11 executable, which has the language code in the filename itself (had to change en-us to pt-br) AND the download URL itself is also different (looked up at Google, it will take you to IE11 download page with all languages, each one has its own URL)!
I downloaded the newest 64 bit Windows 7 Enterprise ISO, and extracted the contents to a folder on my C: drive. I followed your instructions, installed WUD, downloaded all the updates to a folder, and installed NTLite 1.3.1.5060 64 bit. When I ran NTLite and chose my directory it found the Enterprise OS, no problem. BUT, when I attempt to load it, I get the following error: 2ff7e9595c
Comments