Latest Supermium build displays CryptProtectMemory error on launch with One Core API

[5678e7]

Describe the bug When attempting to launch Supermium after installimg it it displays "The procedure entry point cryptprotectmemory could not be located in the dynamic link library progwrp.dll" This happens even after adding environment variables like --no-sandbox to the supermium shortcut as well as using the xp api changed to progwrp.dll as provided on another site.

To Reproduce Steps to reproduce the behavior:

1. Go to your Desktop shortcut for Supermium
2. Click on it twice
3. Wait up to three seconds.
4. Then you see the message

Expected behavior Every time you attempt to run Supermium you will receive this programming error

Desktop (please complete the following information):

• OS: Windows XP Media 'Center 2002 with service pack 3 32 bit
• Supermium 126.0.6478.249 R3 (XP x64 Hotfix)
• Dell Dimension 4600 2 GB of RAM

Additional context

Supermium ran before One Core API 4.0.0-rc4-20240817-experimental.zip was extracted and installed. I suspect One Core API broke something. I observed a few Chromium builds over 105 will crash before it hits about 200,000 K in one or more of the tasks listed in the services tab of task manager or load but never really display anything but the outline of the browser while repeatedly causing windows to generate a message indicating that the program has a problem and needs to close over and over again. This is especially the case with another browser-Thorium

[Half-Modern]

Supermium ran before One Core API 4.0.0-rc4-20240817-experimental.zip was extracted and installed. I suspect One Core API broke something.

Then report it to One Core Api, not here!

[p1glynlol]

Rename progwrp.dll to progwrp.bak on System32 (NOT ON SUPERMIUM FOLDER), restart and try to launch Supermium.

This had nothing to do with Supermium, it's One-Core-API using it's own progwrp.dll to fix the TLS conflict (which was allegedly fixed). And the DLL is not compatible with 126.

Then report it to One Core Api, not here!

They're working on it.

[5678e7]

Rename progwrp.dll to progwrp.bak on System32 (NOT ON SUPERMIUM FOLDER), restart and try to launch Supermium.

This had nothing to do with Supermium, it's One-Core-API using it's own progwrp.dll to fix the TLS conflict (which was allegedly fixed). And the DLL is not compatible with 126.

Then report it to One Core Api, not here!

They're working on it.

This worked. However, now Supermium crashes. with a "need to close" message.

Had a bit more success using the win xp api and its modified progwrp.dll but here it crashes on loading any site. But at least the browser opens

[Stepman123]

--disable-encryption ? --no-default-browser-check --disable-logging --disable-sync --disable-breakpad --disable-component-update --disable-background-networking --disable-machine-id --disable-encryption --no-sandbox ?

[5678e7]

--disable-encryption ? --no-default-browser-check --disable-logging --disable-sync --disable-breakpad --disable-component-update --disable-background-networking --disable-machine-id --disable-encryption --no-sandbox ?

none of these make much difference on the supermium installation that is the main subject of the original post.

To a modified Supermium installation with chrome api adapter. the second set of commands seemed to allow that installation to load to the point where you could load a website within three to five minutes supermium crashes.

With only disable encryption involved something similar to the preceding paragraph happens but Supermium is more likely to fail to open

[GeorgeK1ng]

Close your issue related to other product here. Report in on OneCoreApi instead. There is no place for fixing other projects.