mjd79

What punishment, do you watch what you write? Your advice sent to this user was not copyrighted, so neither will you prove to him that it happened at all. You can ban me for innocence, go ahead, I don't decide about that.

Why are you taking my words out of context???? I wrote that I know more than you in the topic of the unsuccessful @msquidpl tries.

My version not in the literal sense. It simply means the one modified by me that I am currently using. I know this guy from Discord, from him I received advice. I know perfectly well that he did not come up with it himself. On the subject of clumsy attempts I know more than you I'm not going to make this widely available and promote it as my project, I'm simply reporting that this version works. This will be for my use or possibly for those interested from the forum.

At this point I am unlikely to be able to do it, even on Windows 8.0 this build does not work.

Nevertheless, I prefer my version 113.0.5645, which has the right codecs and embeded videos and sync work on it

The latest Chromium 113 build runs on Windows 8.1.

Perhaps this tool will help you - I used to update Windows 8.0 with it Sorry for the Polish download link, pobierz means download. https://programy.net.pl/program,windows-update-downloader.html The program itself is in English anyway. I can also send you a link to a version with integrated updates post EOL until July 2021, created by a well-known and trusted Polish modder, but in an English version, as long as you are willing to install it from scratch

The thread is about preferred versions of W10.... In the case of Windows 7, there isn't even much to choose between, well maybe between build 7600 and 7601 (SP0/SP1) Personally at this moment I am using Windows 10 21H2 LTSC on my main computer, I have never been so happy with W10

Sorry for the offtopic, but why does it take ages to download the extended kernel or anything else from blackwingcat's site? The speed is a dozen kbps regardless of the link.

It just turned out that... the second Ethernet port on the motherboard works, only for some reason its controller was disabled in the BIOS. I have always been convinced that he does not work. Problem solved

I don't want to, it is more profitable to buy something newer

It will also work for Windows 7. In this menu, enable both SSL 2.0 and 3.0, and TLS 1.0, 1.1, 1.2.

I used W10 1511 until very recently, 99% of "ordinary" Win32 applications worked, while the store is dead. From what I gather, the same will happen to the store on version 1607 of LTSB after installing it by unofficial methods.

This is what I will do. Although it's a slight shame, because this network card would be completely sufficient.

As far as I know, the only thing different between 111 and 112 was the DiscardVirtualMemory function, which had to be replaced with VirtualAlloc. This was build 5570.

Hi, the integrated network card in my computer is probably broken... I found an old 3COM on PCI, unfortunately it only has drivers for 32 bit systems. I am not able to install it through the device manager because the architecture does not match. Is it possible to get around this somehow? Thank you in advance for your answer

I also change systems frequently

I see that you have changed to Windows 7. Good decision, because at the moment even XP x86 is already better than Vista x86 due to the existence of Open Core API.

The 472 driver will 99% not work! You need to create an osver.ini file (In the thread below you will find information about what it should contain) Even so, you are bound to get a BSOD or error code in the device manager anyway. The 372 driver is too old to support RTX. Perhaps version 398 modified by win32 will be able to support your graphics card after modifications, but it is unstable probably. There is no point in using anything newer than the 900 series on Windows Vista, or the 1000 series on modified drivers.

Probably the last 100% working stable version at this point is 110. On the other hand, from the "dev/canary" channel I managed to run probably build 5545 as the last one with the help of a user who unfortunately "escaped" from the forum....

Redirect the original ole32.dll file locally, perhaps it will help.

All you need to do is delete the updater.node file.

You need to download Dependency Walker in the appropriate version (x86 or x64) for the gallery, otherwise nothing meaningful will result.

@Zoomer88 You must use the revised version of the March 9 extended kernel, it is available in the mega.nz folder. This version fixed the bug you are talking about.

Check this application with Dependency Walker.