[Bug Report] *Firefox 129.0/Librewolf 129.0* onwards doesn't work on Windows 7 using VxKex 1.1.2.1428

[barkoder]

Application Information:

• Application: Librewolf 129.0
• Download Link: https://gitlab.com/api/v4/projects/44042130/packages/generic/librewolf/129.0.2-1/librewolf-129.0.2-1-windows-x86_64-portable.zip

Description:

VxKex works with Firefox 128.

But Firefox/Librewolf 129 onwards doesn't work with VxKex. It works for a while, then it crashes with an error - LibreWolf could not be started. Exit code: -1073741819

The workaround of setting browser.taskbar.lists.legacyBackend to true in about:config to stop Firefox from crashing after a while(which used to work until Firefox 128.0), no longer works from version 129 onwards.

Problem:

1. Extract Librewolf from Download Link.
2. Enable VxKex 1.1.2.1428 for all executables in the directory and subdirectories.
3. Run Librewolf-Portable.exe
4. Quickly go to about:config and Set browser.taskbar.lists.legacyBackend to true .
5. Close Librewolf and Run Librewolf-Portable.exe again.
6. Do regular browser stuff.
7. Crashes with error LibreWolf could not be started. Exit code: -1073741819

Environment:

• Operating System: Windows 7 x64 Ultimate
• VxKex Version: 1.1.2.1428

VxKex Logs (Required):

Pass - vxkexiscool Logs.zip

P.S.

I'm aware r3dfox is a thing. But I have no idea how @Eclipse-Community got Firefox running on Windows 7.

[YuZhouRen86]

VxKex NEXT supports Firefox 134, Chromium 132 and Librewolf 134.

[barkoder]

I tested Librewolf 129. It works with VxKex NEXT.

I then tested Librewolf 134 portable. I open Librewolf 134. Visit any address. It immediately hangs completely and doesn't crash. I had to kill it with taskkill /F /IM librewolf.exe , which then gives an error LibreWolf could not be started. Exit code: 1

Let me know if you need logs.

Thanks @YuZhouRen86 for the help.

[barkoder]

Also @YuZhouRen86 I tested ungoogled-chromium version 132 - https://github.com/macchrome/winchrome/releases/download/v132.6834.97-M132.0.6834.97-r1381561-Win64/ungoogled-chromium-132.0.6834.97-1_Win64.7z

I get a ungoogled-chromium\chrome.exe is not a valid Win32 application. error.

[YuZhouRen86]

Also @YuZhouRen86 I tested ungoogled-chromium version 132 - https://github.com/macchrome/winchrome/releases/download/v132.6834.97-M132.0.6834.97-r1381561-Win64/ungoogled-chromium-132.0.6834.97-1_Win64.7z

I get a ungoogled-chromium\chrome.exe is not a valid Win32 application. error.

This is the CpiwBypa bug in all versions of VxKex (NEXT), and it is really difficult to fix. Restart your computer and try to launch chrome.exe, or open global settings and see if bypass option checked.

[YuZhouRen86]

I tested Librewolf 129. It works with VxKex NEXT.

I then tested Librewolf 134 portable. I open Librewolf 134. Visit any address. It immediately hangs completely and doesn't crash. I had to kill it with taskkill /F /IM librewolf.exe , which then gives an error LibreWolf could not be started. Exit code: 1

Let me know if you need logs.

Thanks @YuZhouRen86 for the help.

I have LibreWolf portable 134. When I open it, it will stick at white window for a minute, then it will response, and everything will be ok. It is the same issue as Firefox 134.

[barkoder]

~~*I figured out what the reason was for LibreWolf 134 not working with VxKex NEXT - Starting in Offline mode.~~

~~I always start my web browser in offline mode using start "" "<PATH-TO-librewolf>\LibreWolf-Portable.exe" --offline~~

~~I tested all Librewolf 128-133 . All of them work with --offline except for Librewolf 134.~~

~~Removing the --offline fixed the hang.~~

EDIT: No, still hangs. Crashed when I played https://upload.wikimedia.org/wikipedia/commons/transcoded/6/60/PSA_Airlines_flight_5342_crash.webm/PSA_Airlines_flight_5342_crash.webm.480p.vp9.webm

---

This is the CpiwBypa bug in all versions of VxKex (NEXT), and it is really difficult to fix. Restart your computer and try to launch chrome.exe, or open global settings and see if bypass option checked.

I did all of those. Still getting the error when I double click chrome.exe from https://github.com/macchrome/winchrome/releases/download/v132.6834.97-M132.0.6834.97-r1381561-Win64/ungoogled-chromium-132.0.6834.97-1_Win64.7z

Out of curiosity, did you test this particular ungoogled chromium with VxKex NEXT on your Win7x64 computer, @YuZhouRen86 ?

[YuZhouRen86]

~*I figured out what the reason was for LibreWolf 134 not working with VxKex NEXT - Starting in Offline mode.~

~I always start my web browser in offline mode using start "" "<PATH-TO-librewolf>\LibreWolf-Portable.exe" --offline~

~I tested all Librewolf 128-133 . All of them work with --offline except for Librewolf 134.~

~Removing the --offline fixed the hang.~

EDIT: No, still hangs. Crashed when I played https://upload.wikimedia.org/wikipedia/commons/transcoded/6/60/PSA_Airlines_flight_5342_crash.webm/PSA_Airlines_flight_5342_crash.webm.480p.vp9.webm

This is the CpiwBypa bug in all versions of VxKex (NEXT), and it is really difficult to fix. Restart your computer and try to launch chrome.exe, or open global settings and see if bypass option checked.

I did all of those. Still getting the error when I double click chrome.exe from https://github.com/macchrome/winchrome/releases/download/v132.6834.97-M132.0.6834.97-r1381561-Win64/ungoogled-chromium-132.0.6834.97-1_Win64.7z

Out of curiosity, did you test this particular ungoogled chromium with VxKex NEXT on your Win7x64 computer, @YuZhouRen86 ?

Chromium 134 canary latest version test passed. Will be fixed on 1.1.2.1440. Google services are banned here in China mainland (except Chrome stable), so it is very difficult to download canary Chromium. I get it from a GitHub link pointed to Google's API.

[YuZhouRen86]

~~*I figured out what the reason was for LibreWolf 134 not working with VxKex NEXT - Starting in Offline mode.~~

~~I always start my web browser in offline mode using start "" "<PATH-TO-librewolf>\LibreWolf-Portable.exe" --offline~~

~~I tested all Librewolf 128-133 . All of them work with --offline except for Librewolf 134.~~

~~Removing the --offline fixed the hang.~~

EDIT: No, still hangs. Crashed when I played https://upload.wikimedia.org/wikipedia/commons/transcoded/6/60/PSA_Airlines_flight_5342_crash.webm/PSA_Airlines_flight_5342_crash.webm.480p.vp9.webm

---

This is the CpiwBypa bug in all versions of VxKex (NEXT), and it is really difficult to fix. Restart your computer and try to launch chrome.exe, or open global settings and see if bypass option checked.

I did all of those. Still getting the error when I double click chrome.exe from https://github.com/macchrome/winchrome/releases/download/v132.6834.97-M132.0.6834.97-r1381561-Win64/ungoogled-chromium-132.0.6834.97-1_Win64.7z

Out of curiosity, did you test this particular ungoogled chromium with VxKex NEXT on your Win7x64 computer, @YuZhouRen86 ?

Are you getting entry point error? If yes, it is the bug in current version of VxKex NEXT. Google Chrome works well, it only affects ungoogled chromium.

[thatguy344]

Can confirm that Firefox 129 won't even install with the current VxKex release. I'm on W7 x64 and still had an older VxKex release installed (from the original dev) which didn't even manage to get to the "Extracting" stage of the installer - With the current release from this repo, the installer extracts successfully but then somehow still detects W7 and complains about needing to be run in W10, even with "stronger version reporting" enabled in VxKex. Guess i'll try my luck with FF128, then.

Edit: Waterfox won't work with the current VxKex release either, i'm getting "This version of Waterfox requires Windows 10" after extraction here as well. I also tested out Librewolf while i was at it, getting the two error messages "The procedure entry point GetSystemCpuSetInformation could not be located in the dynamic link library kxbase" and "Couldn't load XPCOM" in successive order when i try running that one. Would have been nice to get these W10+ browsers running on this config, but luckily it's not like there aren't any alternatives available.

[CommonLoon102]

https://github.com/e3kskoy7wqk/Firefox-for-windows-7

https://github.com/e3kskoy7wqk/Chromium-for-windows-7

[YuZhouRen86]

Can confirm that Firefox 129 won't even install with the current VxKex release. I'm on W7 x64 and still had an older VxKex release installed (from the original dev) which didn't even manage to get to the "Extracting" stage of the installer - With the current release from this repo, the installer extracts successfully but then somehow still detects W7 and complains about needing to be run in W10, even with "stronger version reporting" enabled in VxKex. Guess i'll try my luck with FF128, then.

Edit: Waterfox won't work with the current VxKex release either, i'm getting "This version of Waterfox requires Windows 10" after extraction here as well. I also tested out Librewolf while i was at it, getting the two error messages "The procedure entry point GetSystemCpuSetInformation could not be located in the dynamic link library kxbase" and "Couldn't load XPCOM" in successive order when i try running that one. Would have been nice to get these W10+ browsers running on this config, but luckily it's not like there aren't any alternatives available.

GetSystemCpuSetInformation bug is already fixed in 1.1.2.1436. Enable VxKex NEXT and report version to Win10, and run setup with Admin, setup will work.

[badrelmers]

the latest VxKex NEXT 1.1.2.1439 works very well with chrome v133 but only x64, chrome x32 does not run, i downloaded the x64 from here GoogleChromePortable64_133.0.6943.60_online.paf.exe

download it run the exe it will download the full chrome as a portable version, once downloaded go to App\Chrome-bin , this is the original full chrome x64 version

---

chromium have problems both x32 and x64 , i tested v132 and v133 chromium 132 x64 did not work chromium 132 x32 works but with workaround, first with vxkex next it gave this error`

[9200:8344:0209/094950.487:ERROR:gpu_process_host.cc(975)] GPU process launch failed: error_code=17
[9200:8344:0209/094950.487:WARNING:gpu_process_host.cc(1418)] The GPU process has crashed 12 time(s)

i solve it by using this flag --disable-gpu-sandbox , but chromium crash sometimes when i open a menu!

to solve it i used --no-sandbox and it worked perfectly, no crash at all, but --no-sandbox is not good for chromium security

to use those flags you have to use winvertroll.exe drag chromium.exe and drop it over winvertroll.exe, now apply Vxkex Next as usual, now you can run it from command line: chrome.exe --user-data-dir=vvv --disable-gpu-sandbox or chrome.exe --user-data-dir=vvv --no-sandbox

i tested with this chromium version chrome-win.zip https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/1381560/

---

ungoogled chromium 132 x64 did not work, it ask for GetPackagePathByFullName function

even the original ungogled chromium x32 v132 did not work , it simply crashes

[YuZhouRen86]

the latest VxKex NEXT 1.1.2.1439 works very well with chrome v133 but only x64, chrome x32 does not run, i downloaded the x64 from here GoogleChromePortable64_133.0.6943.60_online.paf.exe

download it run the exe it will download the full chrome as a portable version, once downloaded go to App\Chrome-bin , this is the original full chrome x64 version

---

chromium have problems both x32 and x64 , i tested v132 and v133 chromium 132 x64 did not work chromium 132 x32 works but with workaround, first with vxkex next it gave this error`

[9200:8344:0209/094950.487:ERROR:gpu_process_host.cc(975)] GPU process launch failed: error_code=17
[9200:8344:0209/094950.487:WARNING:gpu_process_host.cc(1418)] The GPU process has crashed 12 time(s)

i solve it by using this flag --disable-gpu-sandbox , but chromium crash sometimes when i open a menu!

to solve it i used --no-sandbox and it worked perfectly, no crash at all, but --no-sandbox is not good for chromium security

to use those flags you have to use winvertroll.exe drag chromium.exe and drop it over winvertroll.exe, now apply Vxkex Next as usual, now you can run it from command line: chrome.exe --user-data-dir=vvv --disable-gpu-sandbox or chrome.exe --user-data-dir=vvv --no-sandbox

i tested with this chromium version chrome-win.zip https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/1381560/

---

ungoogled chromium 132 x64 did not work, it ask for GetPackagePathByFullName function

even the original ungogled chromium x32 v132 did not work , it simply crashes

Ungoogled Chromium bug has been fixed and it will work in the next release version. Chrome x32 problem is quite difficult to solve, because there was no valid error in log file.

[badrelmers]

@YuZhouRen86 thank you for your great work

I did some investigation about x32, and here are the results if it helps: from v110 to v124 they work fine with vxkex Next and --no-sandbox

from v125 and v126 something changed and an error is shown but chrome still worked GoogleChromePortable125.0.6422.142 works fine with vxkex Next and --no-sandbox

[9636:748:0211/023818.046:ERROR:check.cc(375)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[9636:5992:0211/023818.093:ERROR:check.cc(375)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[9636:748:0211/023818.093:ERROR:check.cc(375)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

GoogleChromePortable126.0.6478.183 works fine with vxkex Next and --no-sandbox

[11856:3024:0211/024547.239:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[11856:1956:0211/024547.285:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[11856:3024:0211/024547.285:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[11856:3024:0211/024547.285:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[11856:3024:0211/024547.285:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

GoogleChromePortable_127.0.6533.120 fails even with vxkex Next and --no-sandbox from v127 the error changed from ERROR to FATAL

[5220:7076:0211/022701.938:FATAL:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

GoogleChromePortable129.0.6668.101 fails even with vxkex Next and --no-sandbox

[3816:5916:0211/030629.741:FATAL:check.cc(360)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

GoogleChromePortable_130.0.6723.117 fails even with vxkex Next and --no-sandbox and does not show the check.cc error

Conclusion:

from v127 chrome stopped working and the error changed from ERROR to FATAL i disabled the features added in v127 that they were not in v126, but chrome did not work

--disable-features=AdditionalOpaqueOriginEnforcements,WebAppSystemMediaControls,WebAssemblyMemory64,CrabbyAvif,DisableThirdPartyStoragePartitioningDeprecationTrial2,FencedFramesReportEventHeaderChanges,NavigationPredictorNewViewportFeatures,DedicatedWorkerAblationStudyEnabled,Prerender2NoVarySearch,Prerender2WarmUpCompositor,OptimizeLoadingDataUrls  --disable-blink-features=AllowJavaScriptToResetAutofillState,AudioContextOnError,AudioContextPlayoutStats,Canvas2dGPUTransfer,CredentialManagerReport,CSSAnchorScope,CSSLazyParsingFastPath,CssRubyAlign,CSSScrollSnapChangeEvent,CSSScrollSnapChangingEvent,CSSTransitionShorterSerialization,DisableThirdPartyStoragePartitioning2,DispatchBeforeInputForSpinButtonInteractions,DocumentInstallChunking,DocumentPictureInPictureUserActivation,IgnoresCSSTextTransformsForPlainTextCopy,InlineBlockInSameLine,InputClipRulesCss,LastSuccessfulPositionOption,LayoutSegmentationFastPathForObjectReplacement,LimitThirdPartyCookies,PaymentLinkDetection,RecollectInlinesReserveCapacity,RTCRtpTransport,RubyShortHeuristics,ServiceWorkerStaticRouterTimingInfo,ShowPickerConsumeUserActivation,SvgFilterUserSpaceViewportForNonSvg,TestFeatureStable,TextSizeAdjustImprovements,UnblockTouchMoveEarlier,UseUndoStepElementDispatchBeforeInput,ViewTransitionDisableSnapBrowserControlsOnHidden,ViewTransitionTreeScopedNames,WebGPUAdapterInfoAttribute

I had read somewhere in the chromium source code that they will treat the ERRORs as FATAL, so maybe this is the cause of the problem

[Neustradamus]

For example, Opera 118.0.5461.41 has same error: "GetPackagePathByFullName" -> kxbase.

It is linked to Chromium based browsers.

Same error: "GetPackagePathByFullName" -> kxbase:

• https://github.com/macchrome/winchrome/releases

Windows 10/11 builds:

• https://github.com/win32ss/supermium/releases

Linked to:

• https://github.com/i486/VxKex/issues/140
• https://github.com/dotexe1337/VxKex/issues/23
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/62

[Neustradamus]

In more, I have discovered in all recent Chromium based browsers, the CTRL+S (or from right click) does not show the window to save...

Same when we try to change the "Downloads" folder:

• chrome://settings/downloads
• brave://settings/downloads
• opera://settings/?search=download

Same problem with:

• Ungoogled Chromium: https://github.com/ungoogled-software/ungoogled-chromium-windows/releases

Note: It works perfectly with the Supermium "Windows 7" builds like:

• https://github.com/win32ss/supermium/releases
• https://github.com/win32ss/supermium/releases/tag/v132-r2
• https://github.com/win32ss/supermium/releases/download/v132-r2/supermium_132_64_setup.exe

Linked to:

• https://github.com/i486/VxKex/issues/141
• https://github.com/dotexe1337/VxKex/issues/24
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/63

[Neustradamus]

It is linked to:

• https://github.com/i486/VxKex/issues/6
• https://github.com/i486/VxKex/issues/84
• https://github.com/i486/VxKex/issues/91
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/2
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/4
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/45
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/57
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/100

[Neustradamus]

I have done a new ticket when we launch an application:

• normally
• in command line

Normally:

• https://github.com/i486/VxKex/issues/183
• https://github.com/dotexe1337/VxKex/issues/68
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/141

Command line:

• https://github.com/i486/VxKex/issues/177
• https://github.com/dotexe1337/VxKex/issues/67
• https://github.com/YuZhouRen86/VxKex-NEXT/issues/140

Do not forget to comment, to confirm, etc.

[Neustradamus]

@YuZhouRen86: I have found:

No more "XYZ is not a valid Win32 application" dialogs!
https://github.com/arkq/winpefix

It can help?

@arkq: Can you help to solve this problem in CpiwBypa / VxKex?

[Neustradamus]

GetSystemCpuSetInformation is linked to:

• https://github.com/YuZhouRen86/VxKex-NEXT/issues/84
• https://github.com/i486/VxKex/issues/84
• https://github.com/i486/VxKex/issues/78