ShadowWhisperer
script does not support Windows 10 32-bit systems (x86)
Do you get an error, or what does it do? .exe or batch script ?
*I don't have access to a 32bit machine to check.
@ShadowWhisperer, the core issue is with setup.exe (https://github.com/ShadowWhisperer/Remove-MS-Edge/tree/main/_Source), compilation platform: AMD64 (64-bit), and don't worry about the script, it's i386 (32-bit).
Proofs:
Possible solution: use the 32-bit version of setup.exe, since AMD64 (x86_64) is backward compatible with 32-bit (but I'm not sure about stability)
well, looks like you can help with it: i assume that you have access to pure x86 and so you have a copy of x86 installation image(or, to dl image from officials, you have 2 days). afaik 19045.5965 x64 (ju?e 2025) shipped with v92(repo - v90) and its uninstaller can be used for purposes of this tool. with the archive in the mind rest should be obvious
note: python and batch, both versions checks for hash of setup.exe so you cannot simply replace it localy. atleast not with compiled python version. batch version, however, can be adjusted by yourself
Batch scripts should be working. I say should since I can't test it without a 32bit machine.
Scripts check the architecture and then downloads the appropriate setup.exe
*I have to do the python versions, yet
If necessary, you can simulate 32-bit development by installing VMware Workstation; I encountered the same error where it failed to open on my computer. I've attached the download link: https://github.com/201853910/VMwareWorkstation?tab=readme-ov-file#vmwareworkstation-17
magnet:?xt=urn:btih:288fe75ce2ac4ddbe87ef49c44675b879b7fb15c&dn=zh-cn_windows_10_consumer_editions_version_22h2_updated_sep_2025_x86_dvd_4a22741d.iso&xl=4998483968
Translated with DeepL.com (free version)
@weix2025, greetings.
Could you please clarify: did you download the release or the batch files (https://github.com/ShadowWhisperer/Remove-MS-Edge/tree/main/Batch)?
I won't be able to check this specifically on the Windows image you provided anytime soon, due to a lack of peers in neighboring countries
@weix2025, The batch scripts work fine (also works on the provided image). The release is a compiled Python version which isn't ready yet, presumably due to a lack of x32-bit support (as I understand it).
video proof:
https://od.lk/s/ODRfODU1NDkzODRf/2025-11-16%2018-17-19.mp4
(Sorry, I just couldn't attach the file to GitHub—constant failure. I hope OpenDrive is accessible for you)
kind of angry offtop
... i'm impressed that you both still kind enough to continue solving this issue author provides no info about issue, abandoned it for about two months and now pops out like a your word(-s) here with just few links and statement like "here a tools, solve it". no thanks and again no any piece of info about what went(or still going) wrong. even current state of this issue with latest batch version is unclear.
i don't try to hate nor something similar, but
when you have an issue and want it to be solved you must provide as much relevant info as possible for issue reproducing or atleast for tracking what/where/how can go wrong
@Ameterius, can you
- provide the log-file from video?
- check where Edge resides? (usually it should be "%ProgramFiles(x86)%\Microsoft\Edge\Application" )
- run echo %ProgramFiles(x86)% in cmd of 32-bit Windows and provide output ... ...
on 2:27 there a warn in the log file - Edge not found ( below [uninstall().edge.init] )
@XakerTwo
I'm just trying to be kind Y_Y
Just now discovered that Edge is kind of alive. There's no Program Files x86 in 32-bit versions.
Log: log.txt
cmd output: %ProgramFiles(x86)%
... weeel
i found few interesting issues
- log line 37 - file not found(due to %ProgramFiles(x86)% not exists in 32-bit OS)
- log line 80 - wth - there should be something like on line 69, atleast package name
- log line 1956(+ line 2003) - ... my guess it's somehow related to bitness (actually it's a STATUS_NO_TOKEN result of toggling SeTakeOwnershipPrivilege).
first can be fixed easily but i will slightly rearange bitness handling (to single condition) second and third... now i need 32-bit OS installed to investigate, especially 3-rd issue
unfortunately i can't do it right now, probably within next few day
oh btw - i will use en-us locale of win 10 from june 2025
Finally got a 32bit image installed. Turns out you can't boot 32bit Windows 10 on a nvme, SATA only... 32bit was phased out before nvme was a thing (according to ChatGPT). It throws a stornvme.sys BSOD.
Microsoft's newest .iso build is from Dec of '23.
- Updated i386 setup.exe to working version
- Updated 32bit folder support - Changed folder to a variable
Log from updated both.bat Log
Edge should be fully removed.
thank you a lot for your efforts, i'm surprised and not expected this, cuz
second and third... now i need 32-bit OS installed to investigate, especially 3-rd issue
was my thoughts about the need for another VM instance and not asking for help
thank you again now to the log...
1: edge.bat
... ...
206: [uninstall().edge.done]
207: [uninstall().webview.init] <<< what is this!??! O_O it should not be presented in edge.bat version
208: INFO: Could not find files for the given pattern(s). <<< ... both.bat could be unhappy
... ...
2066: -1073741700 <<< should be handled anyway
... ...
2113: Unhandled Exception: System.AccessViolationException ... <<< should be handled anyway
207: [uninstall().webview.init] <<< what is this!??! O_O it should not be presented in edge.bat version
The log above is is from running both.bat
I got the .iso from Microsoft. Download iso instead of the create usb.
@Ameterius & @ShadowWhisperer
looking at logs again i noticed one thing: SID before and after elevation is the same in your environments. question: You did not enable built-in Admin account, right?
... since i almost always enable it, atleast temporary, in my environments SID always changes to built-in account on elevation and this could be the core of issue with toggling SeTakeOwnershipPrivilege - process could be created with slightly different set of privileges(code does not add them, only toggle)
:upd
since i not prepare VM yet, can i ask you
- run instance of powershell from elevated cmd
- list of privileges for this powershell process (as text or screenshot); sysinternals' ProcessExplorer able to provide this info on Security tab of process properties
properties of process in ProcessExplorer(double click on process item or from context menu of process) and in properties window there should be tab "Security" ProcessExplorer itself may require admin right to show them all
soooo, that's much interesting: privilege presented but its toggling failing with error "privilege not found" ... okay, fun investigation confirmed xD
thank you for your help
p.s. i'm not an expert in these things so probably it's me who made a dumb mistake somewhere
1 hour to install and setup VM, then 1 run of short snippet and 2 mins of thoughts...
this elephant was so big that it becomes "invisible" can you spot something wrong in this import of the native function in context of x86(32-bit) ? https://github.com/ShadowWhisperer/Remove-MS-Edge/blob/80a20d7f58f44a38eaf8a48d82be1bee0dbf5cb4/Batch/Both.bat#L665
while on enabling it leads to general failure on disabling it raise unhandled exception and this exception has a damn good vector for check + cause of issue more obvious because less cluttered
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at <...>.NtDll.RtlAdjustPrivilege(UInt64 p, Boolean e, Boolean t, Boolean& l)