AstroSkipper

I didn't say that the files in the client\ofc\glb folder are exclusively for Office 2010 or higher. I said: Inside this folder, there are of course many updates for Office 2007 (12.0.xxxx.xxxx), too. Simply have a look at the xml files inside the cab files! All files with the version number 12.0.xxxx.xxxx are targeting Office 2007. As you already cited the creators of WSUS Offline Update 9.2.6 correctly, the download of updates for older Office versions leads to dynamically determined updates which are also downloaded. Either leave them in that folder or delete them before creating the iso image!

@Cixert Just for testing purposes, I have downloaded all Office 2007 updates again but this time under Windows 10. For this, I used WSUS Offline Update 9.2.6 and the wsusscn2.cab file from 16.07.2018 via Wayback Machine https://web.archive.org/web/20180716122029/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab due to your hint about End of updates in April 2018. And what shall I say? It is still possible. I checked the generated download log, and I compared the downloded files with my old download archive. Only a few downloads failed which can easily be found via Wayback Machine and added. Here is a list of failed downloads: The folder o2k7 wasn't created at all as only these 5 files, whose downloads failed, had to be downloaded into this folder. Therefore, I created it and its subfolders, and then copied all files into. All downloaded files seem to be related to Office. However, I can confirm there are many updates downloaded for higher versions than 12.0.xxxx.xxxx which are not targeting Office 2007 but Office 2010 (14.0.xxxx.xxxx), Office 2013 (15.0.xxxx.xxxx) and so on, all inside the folder client\ofc\glb. So, your cited statement seems to be correct: But these files could be of course deleted if unwanted as the folder client\ofc\glb only contains 570 - 580 files depending on the used wsusscn2.cab version. It should also be mentioned that I have added the following exclusions to the ExcludeList-ofc.txt file as a precaution: Anyway! I would suggest to redownload all Office 2007 updates under the above listed conditions. Cheers, AstroSkipper

@Cixert BTW, thanks again for the hint in terms of the issue getting an empty ExcludeList-superseded.txt file! Now, I am curious about your download sizes for comparison.

Not at all. I could even justify it, but it would be totally off-topic and, to be honest, the obvious doesn't really need to be justified.

The download of all Windows XP x86 updates has also been completed. The download took place under Windows 10 with WSUS Offline Update 9.2.6, the latest version of the wsusscn2.cab file automatically fetched by WSUS and C++ Libraries and .NET Frameworks enabled. Here are my results: Size of the folder client\cpp: 87.6 MB Size of the folder client\dotnet: 960 MB Size of the folder client\win: 148 MB Size of the folder client\wxp: 735 MB The file ExcludeList-superseded.txt was extracted correctly and automatically copied to the exclude folder. The file size is 1.86 MB (1956216 B). So, no need to manually extract and paste. Strangely, despite exclusions (among others ndp48-), a number of ndp48-kb* files were downloaded and saved in the folder client\dotnet\x86-glb where I had to remove them during the last pause before creating the iso image. No idea why they were saved. But all in all, everything worked perfectly. My download log only shows those files as failed downloads already mentioned in previous posts. I added them during the last pause. And regarding the download of Office 2010 updates, the method of injecting an older version of wsusscn2.cab also worked fine, exactly the way I had planned and hoped.

Here are my first results: Size of the folder client\o2k10: 729 MB Size of the folder client\ofc: 5.02 GB As already mentioned, I used WSUS Offline Update 11.9.6. My download log doesn't show any failed downloads. So what sizes did you get? Shall we also compare the number of files in each folder?

I am also doing that under Windows 10 at the moment. Just to see whether there are differences to what I already got under Windows XP.

I already downloaded again all Office 2010 updates using the wsusscn2.cab file archived on 04.05.2021 (inside the cab file, you see the files are from 13.04.2021 ) on archive.org: https://web.archive.org/web/20210504233947/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab. When you're ready, we can compare.

That's what I already did. However, when finished, I got an empty Excludelist-Supersed.txt file.

Official support vs. End of updates (is different) Office 2007 support 2017-10-10 End of updates 2018-04 Office 2010 support 2020-10-23 End of updates 2021-04 Where did you find that? I only found that what I already posted: https://learn.microsoft.com/de-de/lifecycle/products/microsoft-office-2010

No. Taking quotes out of context to interpret or emphasise what the quoter wants to have confirmed is a no-go. Think of Pippi Longstocking! And Caesar had turned many people against him.

As far as I could see, some updates are missing. Now, I am downloading again but using the wsusscn2.cab file from 11.02.2021 which fits in with the fact that support of Office 2010 ended on 13.10.2020.

Some days ago, I downloaded all updates for Office 2010. For doing so, I chose WSUS Offline Update 11.9.6, as more recent versions ditched the support for Office 2010, the OS Windows 10 and the most recent wsusscn2.cab file from the Microsoft Update server downloaded by WSUS Offline Update. As far as I could see, it worked. But I didn't compare it with my download session I performed some years ago. I will add the download size later when I am back at this notebook.

Ok. I will try this one tomorrow. To be more precise, it is from 13.07.2020. I'm curious to see what happens. BTW, I will do it from scratch including C++ Libraries and .NET Frameworks with our exclusions and modifications.

Same here. 0 Byte. I have an old wsusscn2.cab file from 09.12.2019 which I use for WUMT. This file can be downloaded here: https://web.archive.org/web/20191209214827/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab. And here is one from 21.04.2019: https://web.archive.org/web/20190421082203/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab. In any case, I will start a new download session with the one from 09.12.2019. Not today but tomorrow.

I have used the most recent wsusscn2.cab file (687.267.824 B, 11.07.2024) from the Microsoft Update server downloaded by WSUS Offline Update 9.2.6. In the folder client\wxp\deu, I now have 564 updates.

You're welcome. I downloaded all Windows XP updates including C++ Libraries and .NET Frameworks some days ago. I checked the download log in terms of warnings, errors and failed downloads. But I didn't have such errors you listed above. Without any more details, I fear it is impossible to say any meaningful. Thus, I have again checked my log but I can't find such errors. How many updates were downloaded into the folders client\cpp, client\dotnet and client\dotnet\x86-glb? I have 12 updates in client\cpp, 3 updates in client\dotnet and 151 updates in client\dotnet\x86-glb.

There are imaging tools which provide features for creating images from a Windows installation for dissimilar hardware. For example, Macrium ReDeploy or Acronis Universal Restore. Maybe, these programmes can further process such an image to your needs.

The good thing about fairy tales is that they always have an ending.

There are countries that make the world the way they like it. Just like Pippi Longstocking. Laws and morals play no role there.

Maybe for you. Otherwise, the statement you keep making is simply nonsense.

Ok. You're welcome. Maybe, @feodor2 is able to fix the plug-ins (flash) issue in one of his next releases. But one thing is clear. MyPal 68.14.3b performs better than the 68.14.2b release and has been fixed regarding several issues.

@Cixert I only use WSUS Offline Update 9.2.6 for downloading Windows XP updates. The download of Office 2007 updates was just for testing purpose to help you. As I already mentioned, I downloaded all of them in the past. There is nothing new to download anymore. Regarding Windows XP, I deleted all references to files which are not XP-compatible. "I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6" means to remove all these references in the StaticDownloadLinks-dotnet.txt and "and then enabled their download." actually means that I checked the box in the main programme window with the option to download C++ Libraries and .NET Frameworks for the next download session. I wrote that before I found out to better set exclusions. Setting exclusions is very effective to avoid unwanted downloads. And the last pause gives the user the possibility to add missing or remove unwanted files before creating the iso image. Please let me know if now all is working for you regarding the Office 2007 updates as it should! Whether it also works for Office 2003, I can't say anything about as I didn't test it. You have to check this on your own. Greetings from Germany, AstroSkipper

Maybe, this one is already too new. Try one of the versions I linked to! Start with the version from 29.01.2019! You can't manually pause the script as you will never match the right time. WSUS Offline Update actually starts extracting the wsusscn2.cab file immediately after downloading it. Pausing must be carried out in the script using the Pause command. Apart from that, the older version of the wsusscn2.cab file must be inserted several times. With each extraction process, WSUS Offline Update checks whether it is still up-to-date. If not, it downloads the latest version again, which we can't avoid at this point. Otherwise you would have to completely adapt the script for downloading older Office products, which I will not do, of course. Therefore, the Pause command must be placed in the correct position in the DownloadUpdates.cmd script. I have inserted the following in line 978, right before the extracting of Microsoft's update catalog file package.xml: echo The script has paused. Now, you can manually replace the file wsusscn2.cab by an older one. When done, press a key to continue! pause Each time this message is displayed, the wsusscn2.cab file must be replaced. And don't forget to also modify the CreateISOImage.cmd script, as described in one of my previous posts! A positive side effect of the Pause command is of course that you can simply leave the script running unattended and just insert the file and press a key from time to time, no matter when. If none of this works for you again, you're probably doing something wrong. Because it was tested by me and definitely works here.

Just for the sake of comparison, I tested the last version 10.9.2 of WSUS Offline Update, which still supports downloading Office 2007 updates, on a Windows 10 computer. As with Windows XP and WSUS Offline Update 9.2.6, the result is disastrous. Tons of updates are downloaded that have nothing to do with Office 2007. So my method of replacing the wsusscn2.cab file with a suitable one is probably the only way to download Office 2007 updates with WSUS Offline Update today. I suspect that Microsoft has changed the download links for old Office products from a certain version of wsusscn2.cab onwards, although most of the files are still on their servers. All that means we have to be tricky in these days to get such old updates from Microsoft's servers.