AstroSkipper

[Setup] AppName=Thorium [FileToRun] PathToExe=.\Chrome\Application\$AppName$.exe Parameters=--user-data-dir="$Profile$" --no-proxy-server /high-dpi-support=1 /force-device-scale-factor=1 --disable-component-update --use-angle=d3d9 --ignore-gpu-blocklist --single-argument [Environment] Profile=".\Chrome\User Data" This is what I actually meant. PS: Think of the Space Bug! Can you still remember?

Do not remove the [Environment] section! Simply set there your current profile path and replace the path D:\Program Files\Thorium\Chrome\User Data under the [FileToRun] section by your enviroment variable $Profile$.

That's very simple. Perform a right-click on a link to be opened, click on the item "Select a programme" from the "Open with" context menu and point to your 360Loader! When done, an entry is automatically created and stored in the registry under the HKEY_CURRENT_USER\Software\Classes\Applications\360Loader.exe key. From now on, you have an entry in the "Open with" context menu for taking up links by the 360Loader.

You're welcome. BTW, why do you define an enviroment variable $Profile$ when you don't intend to use it?

Are you able to open a link in Thorium via the system context menu "Open with" with your modified 360Loader? I ask you this as taking up a link via the system context menu "Open with" would be the transfer of a link via a command line command that is initiated from the registry. And you said this wouldn't work in your Windows XP system. Right?

I think the problem is the way you usually call up the Thorium browser, or the way you open links in this browser. If you start the browser by applying the THORIUM_PORTABLE.bat file, a link to be opened cannot be transferred to this starter batch file via command line. Even if it is compiled to an exe file. I have tested that. If you start the browser by applying the thorium.exe file, a link can be transferred via command line but then all your flags inside the THORIUM_PORTABLE.bat file will be of course ignored. So, you have to add to those registry settings, where the thorium.exe file is called up, all your command line flags from the THORIUM_PORTABLE.bat file. This problem doesn't exist when calling up 360Chrome. You can successfully start this browser with a website transferred to its starter app 360Loader.exe via command line as a parameter. Try this: 360Loader.exe www.google.de And you will see, it works. And now try this: thorium.exe www.google.de You'll see, it works, too, but all your settings are not applied. However, when you try this: THORIUM_PORTABLE.bat www.google.de then you'll notice that it doesn't work. The browser will be called up but the Google website won't be opened. But when trying this: thorium.exe --user-data-dir="PathToYourUserProfile" --your-flags --single-argument www.google.de You'll see it works. The string PathToYourUserProfile has to be replaced by the complete path to your user profile and the string --your-flags by all your command line flags from the THORIUM_PORTABLE.bat file. The --single-argument flag is the one from the registry settings. Have a look at the files HKCR.reg and HKLM.reg inside the Thorium folder!

Getting a BOSD without a minidump is very rare. Do you really have the creation of minidumps enabled in your system? If so, maybe, the crash was so fast that the minidump couldn't be saved. But that's just an assumption. Besides this issue, we shouldn't forget that Thorium is still under development. I'm not surprised at all that BSODs happen, I'm literally expecting them. That's why Thorium wouldn't become a default browser in my Windows XP system at the moment. There are better alternatives for this purpose.

@Cixert Here are the sizes and number of files more detailed which were downloaded in my WSUS download sessions including the updates I manually added as their download failed: Windows XP x86: Size and number of files in the folder client\cpp: 87.6 MB and 12 files Size and number of files in the folder client\dotnet: 286 MB and 3 files Size and number of files in the folder client\dotnet\x86-glb: 673 MB and 95 files Size and number of files in the folder client\msse\x86-glb: 115 MB and 4 files Size and number of files in the folder client\wddefs\x86-glb: 55.4 MB and 1 file Size and number of files in the folder client\win\deu: 33.1 MB and 19 files Size and number of files in the folder client\win\glb: 115 MB and 4 files Size and number of files in the folder client\wxp\deu: 725 MB and 310 files Size and number of files in the folder client\wxp\glb: 10.0 MB and 3 files Office 2007: Size and number of files in the folder client\o2k7\deu: 430 MB and 3 files Size and number of files in the folder client\o2k7\glb: 31.9 MB and 2 files Size and number of files in the folder client\ofc\deu: 81.8 MB and 7 files Size and number of files in the folder client\ofc\glb: 5.08 GB and 572 files Office 2010: Size and number of files in the folder client\o2k10\deu: 628 MB and 1 file Size and number of files in the folder client\o2k10\glb: 101 MB and 1 file Size and number of files in the folder client\ofc\deu: 19.7 MB and 1 file Size and number of files in the folder client\ofc\glb: 5.00 GB and 200 files @Cixert Please copy this list, replace my values with yours for easier comparison and post it here! BTW, I have always enabled the option for the download of Service Packs. That's probably the reason for the different size of the folder client\wxp compared to yours. And it should be mentioned that Office 2010 is not XP-compatible as this topic here is located in the Windows XP subforum. That's why I downloaded Office 2010 updates with WSUS Offline Update 11.9.6 instead of WSUS Offline Update 9.2.6, BTW. In any case, it is only included here for reasons of comparison regarding downloading updates with WSUS Offline Update in 2024. Greetings, AstroSkipper

The downloads depends on the weather. That's what my grandmother would have said if she were still alive. You are simply great.

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.