STABLE version -- 5.1.1130.129

[Sneisi]

Replace the chrome.dll with the one corresponding to your browser's architecture. This is simply to update the displayed Chromium version; no other modifications have been made.

CentBrowser_(Chromium_136.0.7103.48)_x86_x64.7z

Thank you very much for the Chromium 136.0.7103.48 chrome.dll update.

[Sitego]

can we have a new version of this, please?

Chromium Canary 138.0.7170.0. Replace the chrome.dll with the one corresponding to your browser's architecture. This is simply to update the displayed Chromium version; no other modifications have been made.

CentBrowser_(Chromium_138.0.7153.000_Canary)_x86_x64

[Sneisi]

Chromium Canary 138.0.7170.0. Replace the chrome.dll with the one corresponding to your browser's architecture. This is simply to update the displayed Chromium version; no other modifications have been made.

CentBrowser_(Chromium_138.0.7153.000_Canary)_x86_x64

Thank you very much for the Chromium 138.0.7153.000 chrome.dll update.

Popups at some websites about being recommend to update my browser are gone with the chrome.dll update. But some extensions, like tabVertikal - vertical tabs which require a newer version of Chromium, don't work properly with only a chrome.dll update.

[zoso]

thank you.

[Sneisi]

Plz make a new version ... this one is old enough

Already working on upgrading.

How is the state of working on upgrading?

When can we expect an upgrade of Cent Browser?

I've left some extensions that require upgraded version of Chromium aside long enough. Only a Chrome.dll update is not enough to run some extensions that require an updated version of Chromium.

[Sitego]

Popups at some websites about being recommend to update my browser are gone with the chrome.dll update. But some extensions, like tabVertikal - vertical tabs which require a newer version of Chromium, don't work properly with only a chrome.dll update.

As previously explained, the modification only affects how the Chromium version is reported externally — no actual changes were made to the core functionality of chrome.dll

While the browser may identify itself as Chrome 138, it's still running on Chromium 118. This version spoofing does not enable newer Chromium features or APIs that many modern extensions now require.
In the case of tabVertikal, the extension relies on features introduced in later Chromium versions, particularly those associated with Manifest V3 and updated extension APIs. Some likely reasons it doesn't function correctly include:

• Use of chrome.tabGroups or other newer tab-related APIs, which were introduced or improved in later Chromium versions beyond 118.
  
• Reliance on Manifest V3 service workers, which saw significant performance and stability improvements starting from Chromium 120+.
  
• Dependency on specific UI behaviors or rendering updates tied to newer versions of Chromium — especially relevant for extensions that significantly alter the browser’s tab interface.
  

Since Chromium 118 doesn't support these features natively, and the chrome.dll spoof doesn’t provide actual API-level upgrades, the extension cannot operate as intended.
So while version spoofing might bypass certain website checks, it doesn't provide true compatibility with modern extensions like tabVertikal.

In short, this method is more of a compatibility crutch than a true upgrade — and while software on crutches can still "walk", it’s definitely not the same as having real legs.