Let me know how it went On x86 the script will patch the client with option 2 only (WS2008 only) since this is the only option that still gets updates. The only updates that you will need to install through windows updates will be Ultimate extras, MRT tool and any localized updates you might have. Also if WU offers you the .net 4.6.2 cumulative for October skip it and go into the folder 211-repacks and install Aboddi's repack instead. Let me know how fast wget downloads the updates for your. For me recently it goes very slowly and I try to understand if my ISP is using traffic shaping or it is something else.
So it looks like after running the script I now see a total of 89 updates waiting to be installed. So the good news is that it has worked for me (I was getting an error message previously while attempting to update). The only unusual thing I noted is that the script has to be ran manually after a reboot, but even so It picks up where its supposed to, which is a very helpful thing. I scrolled through the threads above, and removed any spaces in the file paths (which if i read correctly could have been the cause of that), but removing spaces did not seem resolve the issue. Nevertheless I think its quite a commendable job you've done with the scripts.
Oh and by the way the wget download was a little bit slow, it took maybe 30-40 minutes to pull all the files. Not sure how fast my link is though since I was doing it using a public connection.
The spaces shouldn't be a problem anymore. That problem was in the early versions and I have since fixed it (I hope at least). Regarding the restarts maybe something is blocking the key for the restart to be created in the registry. You can check the restart section at the bottom of the waves.cmd to see if anything mismatch for you. You can always check from a path with no spaces and if that alone fixes the issue then let me know because I will have to improve something. The download speed is probably due to microsoft limiting their bandwidth I guess because I have the same problem. Shouldn't be because of wget itself because I get the same problem even when I manually download from the catalog. Not a big deal though since you can just keep the files locally after you finish. (I should probably adapt the files so that it downloads only the appropriate bit architecture at some point.
I just ran #65 script with Windows Vista Ultimate x64 on my ASUS K52Jt Laptop. I had no problems at all. Before I run the script I install all the Hardware Drivers needed, Graphics, wi-fi, ect. I ran 1c Populate full, Then Ran the script, after the wget and Firefox gets installed, I'll wait around until 1c-Populate Finishes. Then Ran 2-Download and extract. I walked away for about a Half hour or so, Then I Ran 3-Waves, Sometimes wave 3 has taken only a few hours and other times its taken more time. So I'll just let it do its thing, I came back to it 6 hours later and noticed its finished, Then I ran the updates in Windows Update. Although this time I did get an error code, not sure why? So I ran abbodi1406 Restore Vista WU , choosing #3 Patch WUC as Server2008 + Vista. Is all updated and running well.
Was the computer idling when you manually scanned for updates? I have noticed a weird behavior with windows update. When you run the command to update windows from the terminal (this is what the script does) you need to let it finish and click only when you get the notification that you have new updates. Else it bugs. In this case you just have to check again manually not a big deal. This is why I write on the message to wait until it finish. If you are wondering if it is working or not you can open task manager and see the RAM consumption which should be about 4GBs.
Yea, is what I was kind of thinking also when it happened. Cause I ran it again on my Gateway SX2110 and when I came back at the end of the day to check, updates were waiting for me.
Don't Windows Server 2008 updates for Windows Vista come to a final end in January 2024? Whatever the final date is, I wonder if there'll be development of an update pack - similar to what Windows 7 has with Simplix. I don't see Microsoft allowing Windows Update to work forever with Windows Vista.
Hello Captain! If I recall correctly from something that Aboddi has said the end could be together with 2008R2 somewhere in 2026. We won't know until the end though. Regarding the WU I don't expect it to work forever either. This is why I have one full offline backup of all the updates (and this is the reason for doing this script in first place). So it it is basically easy for everyone to keep an offline backup instead of just fixing WU and then hope that M$ will play nice. (Just don't delete the files after you install them pretty much). The only files that are not included in the script are the ultimate extras (cab files like dreamscene etc, I don't have links for those), even those I have offline ofcourse. An update pack similar to update seven is beyond my knowledge at this point. I just don't know how to do it. If anyone can direct me I would gladly do something about it. The least I can do ofc is a torrent file with all the updates when ever this day comes.
Windows Server 2008 is for Windows Vista, and Windows Server 2008 R2 is for Windows 7, and it's easy to get them confused. I'm being patient and waiting until February 2024 "patch Tuesday" to see if Windows Server 2008 updates are still available for Windows Vista.
He ment 2008/2008 R2 has the same EOS and ESU dates, and if any extension it will be for both https://forums.mydigitallife.net/posts/1805954/ + download.windowsupdate links hardly get shutdown
The script has been updated with the links of December. The links on the posts are also updated for now but since they are not so important as the script itself I won't be updating them as frequently in the future. Maybe every 3rd month or so. Edit: The script has been updated with the links for January.
@TesterMachineOS It is intended. They are not needed in the current updates set. I just kept them there in case that I would need to enable those features in the feature. If it is indeed the end of line for WS2008 I will just clean up the script. Basically BypassEsu is needed only for the .ndp4.6.2 cumulatives if you are using the m$ installers. I am using abbodi's repacks. The datastore fix is needed if you enable the previous ESU support update which is obselete now any way. It stays there because the problem with the datastrore would reemerge in any given month once we get enough updates. So again it will get cleaned up if it is the end of line. You will notice also that power shell 3.0 is being extracted but ignored by the main script. It is one of those things that I don't dare to automate. Who ever needs power shell 3.0 can do it easily manually.
I understand, although I have my doubts, did this happen because the updates corrupted something? using version 067 of the script I did not get this problem..
The script is the exact same in all those versions. The only thing that I do every patch Tuesday is to add the links for the new cumulative updates and comment out the old ones. Have you tried to install the last cumulative updates after version 67 finished installing? Also note that I have never tested any language other than English. Theoretically you shouldn't have a problem since es-ES is supported by WS2008 but you can never be certain. "Dijo la mosca a la rana... mejor morir en el vino que vivir en el agua!" This comes to mind when I hear of Spain! I have good memories from your country.
Help - does not install net framework update kb5034690. i tried uninstalling all net framework, why the center installed them again and this latest update does not want to install. how to fix this error?