Updates Office 2007.

[AstroSkipper]

15 hours ago, user57 said:

well astroskipper it might be in part off-topic but in sence of a installer question (that came out severial times in many topics now) then its not off-topic

you made a very good job in creating that TLS 1.2 proxy

First thanks! And now just for clarification, I am not the creator of ProxHTTPSProxy.  But I am the creator of the package ProxHTTPSProxy's PopMenu TLS 1.3 3V3.  And as you can see inside the name of this package, it is based on a TLS 1.3 proxy since 2022.
Unfortunately, the rest of your comment does not match our recent discussion about the tool WSUS Offline Update and how one can get Office 2007 updates today. To be honest, I don't understand at all what your comment here is actually referring to. 

Edited August 1, 2024 by AstroSkipper

[AstroSkipper]

15 hours ago, Cixert said:

In summary, in Windows Seven it tries to download 800 unrelated updates and in XP it tries 2529 updates not related to Microsoft Office.

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. 

Edited August 1, 2024 by AstroSkipper

[Cixert]

10 hours ago, AstroSkipper said:

Did you replace the wsusscn2.cab file by an older one which is dated short after the EoS of Office 2007 in 2017 in the way I described in my previous posts?  I checked this method, and it works.  Even under Windows XP. No 2529 updates but 580 related to Office 2007 ofc glb. For me, the wsusscn2.cab file from 12.02.2019 also worked fine. In any case, the most current wsusscn2.cab files do not properly work at all. Too much files are downloaded which are not related to Office 2007.  I have the impression that you haven't read my posts properly.  The proof that my method works is the download log I provided in this post: https://msfn.org/board/topic/181623-updates-office-2007/?do=findComment&comment=1270043 
Try, for example, this one from 29.01.2019: https://web.archive.org/web/20190129233558/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab or this one from 05.10.2017: https://web.archive.org/web/20171005192358/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab

I have tried it with wsusscn2 (2019-04-06).cab and the result is the same. When do you paste wsusscn2.cab? When the process of verifying that the latest version is available is finished, the process of extracting package.xml immediately begins. I have tried to make it as precise as possible.

 

On 7/30/2024 at 9:41 PM, AstroSkipper said:

I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6 and then enabled their download. No errors anymore. After the download of all updates for .NET Frameworks, I additionally removed all downloaded updates for higher versions than 4.0 just before the iso image was created. This measure significantly reduces the overal size.  Personally, I do not really use anymore Microsoft Office but I assume that the dowload of Office updates will also work in the same way as it does for Windows XP updates. I mention this as Office 2007 was actually the topic here. 

I think the problem must be something else, this hasn't worked for me either. The process stops with error 404 even though I follow the steps you indicate.

[AstroSkipper]

3 hours ago, Cixert said:

I have tried it with wsusscn2 (2019-04-06).cab

Maybe, this one is already too new. Try one of the versions I linked to! Start with the version from 29.01.2019!

3 hours ago, Cixert said:

When do you paste wsusscn2.cab? When the process of verifying that the latest version is available is finished, the process of extracting package.xml immediately begins. I have tried to make it as precise as possible.

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. 

Edited August 1, 2024 by AstroSkipper
Update of content

[Cixert]

On 7/31/2024 at 10:52 AM, AstroSkipper said:

I have found a way to make it even easier, faster and, above all, more convenient. You can set exclusions in WSUS Offline Update 9.2.6. To do this, you must insert the following strings in the ExcludeList-dotnet-x86.txt and ExcludeList-dotnet-x64.txt files in the exclude folder:

ndp45-
ndp46-
ndp47-
ndp48-

Doing so, the download of files containing these strings will be skipped. And in order not to miss the right moment to press the pause button when adding the missing updates, you can add the following command in line 3 of the CreateISOImage.cmd file in the cmd folder:

echo The script has paused. Now, you can manually add all updates whose download has failed. When done, press a key to continue!
pause

Cheers, AstroSkipper

Let's see if I do it correctly...
In the folder "exclude" the file ExcludeList-dotnet-x86.txt & ExcludeList-dotnet-x64.txt 
I add these lines, each name with the minus symbol after it.
ndp45-
ndp46-
ndp47-
ndp48-

But this file already contains this line, without me adding it:
ndp35-
And WSUS downloads the .NET 3.5 installer anyway
I think 3.5 should be excluded, so why is it downloaded?


 

8 hours ago, AstroSkipper said:

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. 

I will try it, thanks 

[Cixert]

On 7/30/2024 at 8:41 PM, AstroSkipper said:

I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6 and then enabled their download. No errors anymore. After the download of all updates for .NET Frameworks, I additionally removed all downloaded updates for higher versions than 4.0 just before the iso image was created. This measure significantly reduces the overal size.  Personally, I do not really use anymore Microsoft Office but I assume that the dowload of Office updates will also work in the same way as it does for Windows XP updates. I mention this as Office 2007 was actually the topic here. 

I don't understand your sentence either.
"I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6 and then enabled their download. "

Does this mean you remove the shortcuts to 4.6 and 4.6.2 inside
StaticDownloadLinks-dotnet-x86-esn.txt
and
StaticDownloadLinks-dotnet-x64-esn.txt
in static folder????

I don't understand you delete and then say "and then enabled their download"

Edited August 1, 2024 by Cixert

[Cixert]

I follow your instructions @AstroSkipper
I put download .NET and C++ for Windows XP in Spanish and it tries to download .NET 4.6.2 in German.
Maybe because the program WSUS is made by Germans... 


EDIT:

FIXED:
I have deleted most the links contents in
StaticDownloadLinks-dotnet.txt
Which most contains links in German.
Delete for all languages except German.

Edited August 2, 2024 by Cixert
SOLVED

[AstroSkipper]

On 7/30/2024 at 9:41 PM, AstroSkipper said:

I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6 and then enabled their download. No errors anymore. After the download of all updates for .NET Frameworks, I additionally removed all downloaded updates for higher versions than 4.0 just before the iso image was created. This measure significantly reduces the overal size.  

17 hours ago, Cixert said:

FIXED:
I have deleted most the links contents in
StaticDownloadLinks-dotnet.txt
Which most contains links in German.
Delete for all languages except German.

17 hours ago, Cixert said:

I don't understand you delete and then say "and then enabled their download"

@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 

Edited August 2, 2024 by AstroSkipper
Update of content

[Cixert]

On 8/2/2024 at 1:15 AM, AstroSkipper said:

@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 

Yes, thank you very much, if it weren't for your help I wouldn't have achieved anything. 
After everything works correctly I will make a summary of all the necessary steps.

Let's go by systems, for the moment the question is as follows:

WSUS 9.2.6
option XP x86 with .NET Framework and C++:

Adding these lines to ExcludeList-dotnet-x86.txt & ExcludeList-dotnet-x64.txt does work.
ndp35-
ndp45-
ndp46-
ndp47-
ndp48-

The .NET 3.5 installer is normally downloaded, what is not downloaded are the updates for .NET 3.5 but are for .NET 2.0, 3.0...
The problem was that on my computer WSUS does not work well with the temporary files that contain the download lists, the strange thing is that downloading the XP updates without .NET did work but with .NET it failed.

I have run it on another computer and it worked with the latest wsusscn2.cab version.
The following files are not downloaded but I add them manually thanks to your pause functions on the correct lines:
\client\dotnet
-NDP40-KB2600211-x86.exe
\client\win\glb
-Silverlight.exe
\client\wxp\esn
-wmp11-windowsxp-x86-ES-ES.exe
\client\wxp\glb
-WindowsXP-KB942288-v3-x86.exe

Also I delete for x64:
\client\cpp
-vc_redist_x64.exe (all)
\client\win\glb
-Silverlight64.exe
and...
dotnetfx35langpack_x86de.exe (only for German language)

Now I have this problem in the log and I don't know how to add these missing downloads or what the message exactly means, I see in some old forums that there are more than 2 downloads:
2024-08-02 22:09:12,83 - Info: Downloaded/validated 2 statically defined updates for dotnet x86-glb
failed: Unknown error.
failed: Unknown error.
2024-08-02 22:15:09,45 - Info: Downloaded/validated 14 statically defined updates for wxp esn
failed: Unknown error.
failed: Unknown error.

All other files download correctly, how do I guess which ones are missing?
The error does not occur with the XP option without .NET
I don't know what "statically defined updates" means.
I think it's the links contained in the "static" folder.

EDIT:
I have tried with old wsusscn2.cab (2019-04-06) and these files have been downloaded correctly.
The pity is that this file has 54 dynamic updates less.
I will try to make a mix between both.
And also the pity is that this wsusscn2.cab is dated 3 days before the end of support for Windows XP Embedded.

It seems to make no sense that if they are URLs contained in a .txt file, they are downloaded or not depending on the version wsusscn2.cab and whether or not the .NET option is checked in WSUS.

Edited August 3, 2024 by Cixert
partially solved

[AstroSkipper]

1 hour ago, Cixert said:

Yes, thank you very much, if it weren't for your help I wouldn't have achieved anything. 

You're welcome. 

1 hour ago, Cixert said:

Now I have this problem in the log and I don't know how to add these missing downloads or what the message exactly means, I see in some old forums that there are more than 2 downloads:
2024-08-02 22:09:12,83 - Info: Downloaded/validated 2 statically defined updates for dotnet x86-glb
failed: Unknown error.
failed: Unknown error.
2024-08-02 22:15:09,45 - Info: Downloaded/validated 14 statically defined updates for wxp esn
failed: Unknown error.
failed: Unknown error.

All other files download correctly, how do I guess which ones are missing?
The error does not occur with the XP option without .NET
I don't know what "statically defined updates" means.

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.

Edited August 2, 2024 by AstroSkipper

[AstroSkipper]

1 hour ago, Cixert said:

And also the pity is that this wsusscn2.cab is dated 3 days before the end of support for Windows XP Embedded.

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.

Edited August 2, 2024 by AstroSkipper

[Cixert]

17 minutes ago, AstroSkipper said:

I 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.

The numbers match mine except I have 559 in the folder client\wxp\esn instead of 564.
I'm afraid we both have these files wrong, I just found a major bug. 
I just compared the downloads made by running WSUS 9.2.6 with wsusscn2.cab version 2024 and re-running the same installation with wsusscn2.cab version 2019.
This has preserved the previous downloads.
I expected the difference to be 16 more files with wsusscn2.cab version 2019 but it was only two more:
\client\win\esn
windows-kb913433-x86-esn.exe

\client\wxp\esn
windowsxp-kb923789-x86-esn.exe

But the important error I saw when comparing the "exclude" folder
In 2024
ExcludeList-superseded.txt measures 0 KiB 

In 2019
ExcludeList-superseded.txt measures 1640 KiB

I am reviewing the downloads made for XP with WSUS 9.2.6 without the .NET option and ExcludeList-superseded.txt measures 1911 KiB.

This file is downloaded when running WSUS, it does not come with the program, and with the .NET option checked it is downloaded empty, so we have outdated updates.

Please check how many KiB yours is.

[AstroSkipper]

14 minutes ago, Cixert said:

But the important error I saw when comparing the "exclude" folder
In 2024
ExcludeList-superseded.txt measures 0 KiB 

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.

[Cixert]

9 minutes ago, AstroSkipper said:

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 copied and pasted ExcludeList-superseded.txt with 1640 KiB and ran WSUS with the latest wsusscn2.cab with the "Cleanup download directories" option.
Now 290 updates are downloaded instead of 559 and the folder finally has 303 updates left.
You can try the updated version for XP (without .NET) of ExcludeList-superseded.txt or download this version from 2020-July (latest SHA-1) that they say works from Windows 2000 to Seven.
https://archive.org/details/wsusscn2
It's funny that according to Microsoft the new version works since 2007-March
https://support.microsoft.com/en-us/topic/a-new-version-of-the-windows-update-offline-scan-file-wsusscn2-cab-is-available-for-advanced-users-fe433f4d-44f4-28e3-88c5-5b22329c0a08

But we are already checking that it doesn't work...
What I don't know is if we copy and paste the version for XP without .NET if it will have .NET since I am seeing that the version of ExcludeList-superseded.txt is different for each option checked.

[AstroSkipper]

36 minutes ago, Cixert said:

You can try the updated version for XP (without .NET) of ExcludeList-superseded.txt or download this version from 2020-July (latest SHA-1) that they say works from Windows 2000 to Seven.
https://archive.org/details/wsusscn2

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.

Edited August 3, 2024 by AstroSkipper