ED_Sln

FFmpeg / FFplay cannot be connected to the players, because they cannot be installed as a filter. LAV can be installed, but it has not had updates for a long time, and the latest version does not support AV1.

The h266 codec has already been made, and it goes as a replacement for h264-h265, I wonder when it will be added to PotPlayer.

PotPlayer supports AV1 and works in Win XP.

The problem is in the wpsmain.dll file. If you replace it with the old version or patch xompie, then the office will start. The ksomisc.exe error still appears, but it does not affect the work, it can be deleted, without it there is no error and everything seems to work without problems.

Indeed, there is no binding to languages. But why then did all updates share by language? It was possible to make glb for everyone, and separate for localized ones. As done in the 2007 office.

Ah, they are in the form of cab archives. But still, the 2003 office itself, like XP, accepts updates only in its own language.

Office 2003 has a language binding, the correct update names include themselves and the language, for example: office2003-KB2726929-FullFile-RUS.

The inclusion of international fonts should help if the site does not use any characters that appeared in newer operating systems.

MS does not stop, now other languages have been hidden from the update catalog. Displays updates in the system language only. It's good that I managed to download all the updates for XP, but for the server 2003 and 2003 office - no.

At this time, standard drivers are installed, so if possible, disconnect all devices, network card, sound, usb, additional controllers. And what is the code for the blue screen of death? Perhaps it indicates a problem driver.

AOMEI Partition Assistant work on Win XP: https://www.diskpart.com/download.html

No, the system language is not important, the driver is always in English, all the necessary registry keys are also English. In the driver, only lines with the name of the device can be localized.

No, you cannot restore the system for more than 90 days, old restore points are deleted.

In fact, the number of computers with windows XP installed is much, much larger. Almost all payment terminals, ATMs and cash registers still work on XP. Also, a lot of computers are used in organizations where there is not even access to the Internet. And also in special equipment in hospitals, auto diagnostics and so on.

Then try to roll back the system.

Yes, try to delete it, the installer will check for the presence of the file and install the correct one.

What version of the mso.dll file is? Last working - 14.0.7214.5000. If it is newer, then you need to replace it with this one.

Office updates have long been released separately, on the first Tuesday of the month - non-security updates, on the second Tuesday - security updates. It’s just that the 2010 office did not have non-security updates for a very long time.

Download the update https://www.catalog.update.microsoft.com/Search.aspx?q=kb4092483 try installing, if it says what is already installed, it means that some newer one is installed.

The problem is in updating mso2010-kb4484126, it is also in updates KB4462223, KB4461614, KB4462174. Last MSO update without a problem - mso2010-kb4092483.

Blacklisted drivers can be removed in the config, parameter media.wmf.disable-d3d9-for-dlls. Usually the driver works fine, even if it was blacklisted.

There is no support 1.3, there is only what those updates give. But you can make support using HTTPSProxy. It will decrypt the traffic and forward it to the browser.

This site has switched to TLS 1.3. Or to the combined mode 1.3 and 1.2, but in this case, 1.2 uses encryption that is not available in XP.

Did you configure the registry after installing the updates as described in this article? https://support.microsoft.com/en-us/help/4467770/update-to-enable-tls-1-1-and-tls-1-2-as-secure-protocols-on-winhttp TLS 1.1 and 1.2 should be included in the browser settings, if not enabled, then enable them.