32bit fixed and fully up to date version is up
I've also left 7zip in as a silent install. It's just too useful when I'm working with images. It's easy to remove though if you don't want it installed (GPL anyway and absolutely tiny) - either add / remove programs, or you can just stop the integration by removing it from the batch file.
Originally Posted by Saracen
Just running the patch all for the x86 images
are the errors expected ?Code:FINISHED --2014-10-07 23:07:28-- Downloaded: 3 files, 2.8M in 0.4s (7.34 MB/s) SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = c:/progra~1/wget/etc/wgetrc ./Program/helpers/data/url_list_x32_lateinstall.txt: Invalid URL ::These need installing after others: Unsupported sche e No URLs found in ./Program/helpers/data/url_list_x32_lateinstall.txt. SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = c:/progra~1/wget/etc/wgetrc ./Program/helpers/data/url_list_x32_ie.txt: Invalid URL ::IE11 updates: Unsupported scheme ./Program/helpers/data/url_list_x32_ie.txt: Invalid URL ::These need to be installed last (which is why I use a separat directory): Unsupported scheme ./Program/helpers/data/url_list_x32_ie.txt: Invalid URL httx://download.microsoft.com/download/4/2/C/42C1FDC9-AF3B-4D36 8367-E0D5B2706ADF/IE11-Windows6.1-KB2962872-x86.msu: Unsupported scheme ./Program/helpers/data/url_list_x32_ie.txt: Invalid URL httx://download.microsoft.com/download/1/A/5/1A558D6C-7610-4A9A BA17-56C0E6761B35/IE11-Windows6.1-KB2909210-x86.msu: Unsupported scheme ./Program/helpers/data/url_list_x32_ie.txt: Invalid URL httx://download.microsoft.com/download/2/3/4/234FA790-5193-40D4 84E2-8DEB3AA9A9F6/IE11-Windows6.1-KB2956283-x86.msu: Unsupported scheme --2014-10-07 23:07:28-- http://download.windowsupdate.com/c/msdownload/update/software/secu/2014/04/ie11-windows6.1-kb 929437-x86_cb1f165632046e7241aed6e5cd0979315b318418.msu Resolving download.windowsupdate.com... 62.252.168.152, 62.252.168.153 Connecting to download.windowsupdate.com|62.252.168.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 25625774 (24M) [application/octet-stream] Saving to: `./User/updates/ie/ie11-windows6.1-kb2929437-x86_cb1f165632046e7241aed6e5cd0979315b318418.msu'
Also 208 updates; is that expected too ?
Yup. I use 'hxxp' when I don't want it to download a URL while I'm testing. If I find out I actually needed it, I just swap the x for t.
I should have removed them in the final package, but it'll make no difference. They won't get downloaded (and of course, integrated).
The lines that start with :: are comments. They are not URLs and are only there so I can keep track of which URLs are which in each file. Wget reports this as an invalid URL - which it is...but it's supposed to be
208 Updates is right for SP1 32bit. It's getting close to 300 on x64. Yes - all official updates that will get pushed to you via WU in some form or another. In some cases you'll see less in WU, but that's only because some KB patches contain more than one fix / are system specific. This is designed to be a disk for system admins to not have to worry and always have an up to date (or close) Windows image to work from.
I must stress this - this is a super clean install image, made only using official MS tools. The patches are from MS and signed, so no manipulation of them. It might seem like a lot, but that's because there is and no other reason.
In fact, this is cleaner than installing Windows and then all the patches manually as your WinSxS folder is smaller as a result
I havn't rerun the x64 but last time it was arounf 260 updates, was just checking about the errors has they seemed odd.
Can i make one sugestion [i have no idea how much time it would take or if it is needed] but could you look into a way to auto update the core bits of the patch process. Currently when you update the file that contains all the kb updates you have to upload this then we have to download it; is there not a way to have another standalong script / updater that goes out and checks what it has against what you have ? - sorry if this isn't making sense am just thinking of ways to lighten the workload.
Yeah, I've not updated the x64 yet, but that 260 has more to add now, which probably won't be far off 300.
The patching - this is actually how it was done. I just grabbed the update download list from my server via wget and parsed that. A friend pointed out though that this is actually a security concern for some people: What if I was to swap out the links for something malicious? You'd get a patched image, with added extras which you don't want. With the method as it is now, everyone is free to open up every file and see its contents.
Similar concerns if my webserver died.
Also the update links are just one small part of it - the batch files do the real work. These are usually updated at the same time as the links with improvements / fixes.
If it's a download concern, you can just copy the old downloads into the same new folders under the 'User' area. The scripts will then see the file is already present locally, check it matches the server one, and not redownload it if they are the same.
I'll consider adding it back in at some point if people want it, but it doesn't make my life any easier as I have to worry about mismatching batch and other files. At least when I upload the zip, I know it works as a package and I don't spend time troubleshooting. Keep in mind that most issues I've come across are user error. In fact, everything so far apart from the all images issue with the x32 image.
Last edited by Agent; 08-10-2014 at 10:07 AM.
What ram drive software are you using ?
X86 failing to install inside VirtualBox.
This is the 2nd attempt at patching the x86 image; the first time i used the all images option; this time i did one image at a time [inside a ram disk].
It got past the first part of the set up and now apears to have frozen just sat doing nothing and has been for the last 15mins
<edit>
Looks like it is stuck on the first reboot
Last edited by Apex; 10-10-2014 at 12:06 AM.
Gets past that section and onto first restart, click the restart option and it doesn't restart; sits there like the first image.
Force a shutdown / restart in VB and it boots and continues past the giving computer a name / picking network settings etc and onto finalizing settings and its sat there currently...
forced reset again and now into windows, check on updates - 150 to install....so something defo not right with the install.
B*lls to this, am going to bed.
Last edited by Apex; 10-10-2014 at 01:11 AM.
I thought I would have a go at the 32bit for a comparison using the default downloaded ISO and 0.2b patcher
I did update 1 image (ultimate) and the updates all went in okay it seemed.
I have just installed it using Vbox, allocating 2GB of RAM, 4 cores, 128MB of video RAM (acceleration on), 30GB dynamic vdi on the 30GB RAM drive (soft perfect RAM drive). I am now staring at the enter User name and computer name.
Next > Next > Skip (product key) > Use recommended settings > next > home network > and it moves on to the post install installs.
- its now moved on to preparing desktop after less than 10 minutes
- now restarting and back on the desktop
- win updates reports 2 important and 34 optional
- with 'get other Microsoft updates' enabled it reports - 2 important and 37 optional
All good as far as I can see
Last edited by Kumagoro; 10-10-2014 at 11:03 AM.
Did you land at the desktop Kumagoro?
I'll check things again my end Apex, but I went over it several times and did several test installs without an issue. I've no idea what would cause what you're seeing.
When integrating, do you see them go up to 100%? Are you running the command line as an admin? Are you sure you installed the same version of Windows as you patched. If you patched Ultimate and installed pro for example, you won't have the updates.
Yes its all good
-
Did it again using 32 bit enterprise (all update script)
ISO came out at 3.232GB vs 3.359 for the above.
I have noticed when you do the all image update it does report a lot of errors at the very end after un-mounting and making the ISO. Its so fast that I cannot tell what it is all about though just before the final screen so I can't scroll back to see. This doesn't happen with the update 1 image script.
This happened in the old script as well but I think the ISO worked fine though from that time. I am now in the process of installing enterprise.
- All good as well
Other updates which came down though. I have to say I wasn't paying attention to how full the RAM disk was getting if the updates got integrated etc so I will do it again.
Code:Important KB2604115 KB2656356 KB2779452 KB2742599 KB2789645 KB2894844 KB2931356 KB2937610 KB2943357 KB2972211 KB2973112 KB2758857 KB2813430 KB2862966 KB2868626 KB2871997 KB2918614 KB2973351 KB2982378 KB2685811 KB2836943 KB2685813 KB2726535 KB2732059 KB2750841 KB2763523 KB2773072 KB2798162 KB2808679 KB2820331 KB2843630 KB2852386 KB2868116 KB2893519 KB2908783 KB2966583 KB2973337 KB2985461 KB2998527 KB982018 Optional KB2574819 KB2592687 KB2830477
Last edited by Kumagoro; 10-10-2014 at 01:13 PM.
Agent (10-10-2014)
Space issue - they're some of the last updates (can tell from the high numbering), so they're getting culled because you've ran out of space on your RAM drive. They are all in there - I just checked
I've never tested it on enterprise, but it should work the same.
I just tested the ultimate one I just did and it also comes up with 40 updates after doing the 2....
I will do it again... again
Did Enterprise again with an empty RAM drive which didnt even get close to filling up and after restarting and hitting check for updates it shows
2 imports which goes down to 1 after it must check or auto install.
restarted and re checked still 1
Installed the 1 important (malicious removal tool)
restart and recheck gives only optionals
installed Japanese lang pack, restart and recheck gives install windows update - update
THEN 40 important came in...
+ 5 optionals but two are language packs ...
Mystery solved but I wonder why the 40 importants.
Last edited by Kumagoro; 10-10-2014 at 04:28 PM.
The cmd window is always started in admin mode.
I have patched each image one by one i've also used the patch all option with the same results.
I will wipe the VM tonight when i get home and try again with the iso from MS to see if my VB install is naffed.
Last edited by Apex; 10-10-2014 at 08:41 PM.
Fresh x86 pro iso from MS and it installs fine.
2,564,476,928 bytes
I am currently runing the patch all images with it on a 10GB ramdisk (clean download again of all the 208 patches) - will see how this goes.
Final image file is 3,738,103,808 bytes
And we have a winner; all patched and up and running. I have no idea why it wasn't working before but it is now
Last edited by Apex; 10-10-2014 at 11:15 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
