32-bit
wixmachine scopemsedge.sf.dl.delivery.mp.microsoft.com · publisher domain- File name
- MicrosoftEdgeEnterpriseX86.msi
- SHA-256
- 93d84ee404ae77f6daedc947b16438b217e294979c6e259530fe7df1500de488
- Product code
- {E9256887-0FAD-36D8-B362-43906E3807FD}
by Microsoft Corporation · Microsoft Software License
World-class performance with more privacy, more productivity, and more value while you browse.
Edge ships with Windows, so the usual reason for wanting a standalone installer is reinstalling it after removal, deploying a specific channel across an organisation, or installing on a machine with no connection.
Microsoft publishes standalone Edge installers through its enterprise channel, and those are the ones listed here with their hashes.
Note the channel. Stable is what you want unless you are deliberately testing Beta or Dev builds, which update on a much faster cadence.
These URLs are the ones Microsoft Corporation declares in its own manifest. We do not proxy or shorten them, and we do not host a copy.
More than one architecture below. Check which one your Windows is if you are not sure.
Run this against the file on disk. If the output does not match the hash below, the file is not what Microsoft Corporation published. Delete it.
Windows · PowerShell
Get-FileHash "MicrosoftEdgeEnterpriseX64.msi" -Algorithm SHA256macOS · Linux
shasum -a 256 "MicrosoftEdgeEnterpriseX64.msi"Expected output
716b2549eedf4305b92d149186f878394c8d8b7b743db0eaaec773349ed3c273
Got a different hash, or one you cannot place? Paste it into the hash checker and it will tell you which program and version it belongs to, past releases included.
This installer is an MSI package, so it takes the standard Windows Installer switches. That is a property of MSI itself rather than something the publisher declared.
32-bit · machine scope · MSI convention
msiexec /i "MicrosoftEdgeEnterpriseX86.msi" /qn /norestart64-bit · machine scope · MSI convention
msiexec /i "MicrosoftEdgeEnterpriseX64.msi" /qn /norestartARM64 · machine scope · MSI convention
msiexec /i "MicrosoftEdgeEnterpriseARM64.msi" /qn /norestartRun it from the folder holding the downloaded file, in a terminal opened as administrator when the package installs for all users. Silent means no window and no prompts, so check the exit code rather than waiting for something to appear: 0 is success and 3010 means it worked but wants a reboot.
Silent install commands for every program we index · silent uninstall
Every guide on this tells you to hunt for the product code with Get-WmiObject or in the registry. You do not need to: it is published in the installer manifest, and it is printed below.
Product code · 32-bit
{E9256887-0FAD-36D8-B362-43906E3807FD}
Uninstall, with the usual prompts
msiexec /x {E9256887-0FAD-36D8-B362-43906E3807FD}Silent, for deployment
msiexec /x {E9256887-0FAD-36D8-B362-43906E3807FD} /qn /norestartProduct code · 64-bit
{A36ED5D9-C266-314E-8A5B-3BB5ADE3B65D}
Uninstall, with the usual prompts
msiexec /x {A36ED5D9-C266-314E-8A5B-3BB5ADE3B65D}Silent, for deployment
msiexec /x {A36ED5D9-C266-314E-8A5B-3BB5ADE3B65D} /qn /norestartProduct code · ARM64
{E3019B00-4D0F-3759-BE6A-61046D3256FF}
Uninstall, with the usual prompts
msiexec /x {E3019B00-4D0F-3759-BE6A-61046D3256FF}Silent, for deployment
msiexec /x {E3019B00-4D0F-3759-BE6A-61046D3256FF} /qn /norestartThe codes above belong to Microsoft Edge 151.0.4129.78, the version in our index. If you have an older release installed, its code is different and this command will report that the product is not installed. In that case run Get-Package -Name "Microsoft*" in PowerShell to read the code of what you actually have.
This removes the program as the publisher packaged it. Settings and files created after installation, typically under AppData, are deliberately left behind by the uninstaller and have to be deleted by hand if you want them gone.
Reinstalling and hitting error 1638? That is this same product code, and the command above is the fix.
Product codes for every program we index, with the msiexec switches and how to read the code off your own machine.
The macOS build as Homebrew declares it, with the same treatment as the Windows side: the publisher's own URL and a hash to check it against.
| Signal | Finding | Points |
|---|---|---|
| SHA-256 hash published | 3 of 3 installers ship a SHA-256 hashWithout a published hash there is no way to prove the file you downloaded is the file the publisher built. | 30 / 30 |
| Binary provenance | 3 on the publisher's own domainThe strongest signal against a repackaged installer: the file should come from the publisher, not from a mirror nobody vouches for. | 35 / 35 |
| Served over HTTPS | 3 of 3 over HTTPSAn installer fetched over plain HTTP can be modified in transit. | 15 / 15 |
| Licence declared | Microsoft Software LicenseA declared licence tells you what you are actually allowed to do with the software. | 5 / 5 |
Extensions Microsoft Edge registers itself to handle.
Yes, in the sense we can actually verify: the installer downloads from microsoft.com, which is a domain we have tied to Microsoft Corporation.
Every one of the 3 installers on this page comes with the SHA-256 Microsoft Corporation declared, so you do not have to take our word for it: hash the file you downloaded and compare.
What this does not tell you is whether the software itself is any good, or whether you want what it does once installed. A publisher can ship something you would rather not run and the download is still authentic. We answer the question we can measure and leave the other one to you.
If Windows says “Windows protected your PC” when you run it, that is SmartScreen reporting reputation, not a malware verdict — it shows up on perfectly legitimate software from small publishers and on releases that are simply new. The reverse matters more: no warning does not mean the file was checked.
How the 100/100 score is calculated · why the source matters more than the reputation
Windows ships with a package manager, and this program is in it. The identifier below is the one Microsoft's repository uses, which is also where the download URL and hash on this page come from.
Install
winget install --id Microsoft.Edge --exactUpgrade later
winget upgrade --id Microsoft.EdgeWhy --exact: without it winget matches on name as well as identifier, and a search that returns more than one package makes it stop and ask rather than install. Pinning the identifier is what makes the command safe to put in a script.
Not installing anything, or getting an error back? The commands that actually come up covers upgrading everything at once, what --include-unknown is for, and why winget can be missing from a machine that should have it.
The version history of Microsoft Edge, each release with the download URL the publisher declared at the time and the SHA-256 to check it against. Useful when an update breaks something and you need to downgrade to a build that worked.
We do not host any of these files and never re-upload them, which is the difference between this and an old-version download site.
FC4F505AE0835BB033E970D842893CF1E4EA79E561281984F677B32E2CE20AB3
EDF3E24EB291B26BBD09C0A7477E30CE32897E4692743B47961CC40C0CFA8685
2A9D69E18A5865054CD76BBEB8E2AC415D75B78FBC0FC1C4BD6894E856BDDC17
F9BEBDB2CF1442E6067CE32B9159B8423C871E61A2AEA3814DF74DD59D7817C8
AD2FB7B3BD49564D0967C4EB0B0307D5420A9636E8E2F479E7FFC4E8B7B86AE6
572DBED15B934CDC0DB250F749D86D9BE634E35D455BDFA9A7CFFF25331F4DAB
38DD57678430B4E4675C9DD95453C3EDE462FA33FF026D33233DF63E40CC53D1
E8F3EEBED93FE98FD60F36749B0CB2D26E31FB8F704EA4700B7C68634FAFC753
9D55325985796A404A0C275C5A886B5C2BFD712D79471106C31D12526F77CD48
08DB9851C44DB4EC65A9897403B391E1C76E5FED9BF150386DB411C13A3E074C
CE3C976D8E624756F845F0AD1FC80E31E6099DB56A19FA8CE8341AFE44B325B1
62723871717752F5D900A7754B1D653F05D12AC36A0A8D051C09FAC64DCF105A
A0C619304DE94B2B491ABC4833FA6850DBF9F10E8BE53D06CA9624B465760D2A
C50452BAF080C01BE2E3D5516B2618255515BD467AC346E5E95B142FE308A7C3
25E50E103385CA35F21B7456A75D13CCAF7123F8BD0DDA6AECD3D13299FEBA04
4728A7D088B2E2F6A12FD0EF2C1B148A9CFF9E55E6442A99CE4C7AEC75C6292A
1EFF2543FF905276BF16B3C2B508FFA97ED52E7B96F122C310C1FF5D42238EC1
078C0200619CD16018350E7BE94BA7731E4032F58575DA16506D6E0D1E9AAE3D
B184CE6A9F4D73B16D766F0D8A96A2DF9175573E40BBAF30746E04ACA563C0E7
037340DC31DC0D2DD6C0D7E7627064B3F34B03656D37A7CAB499F4E8A1697882
61EF15751FD9C6B3D7B03A178E1A2F7CA91096EAEF1814E7CE37ACB7B68EA8D8
C0F94281DA80755398FF01ED2CA6CF4B2EC23931983FBA002AA76216B3E4B3C0
94A406CDC1AB9C1C8AC8AA48B42D89E4E35CEE68622CDA718B301E5E3ED93B49
77800380B91165F60FF70E377C41F6540B011E3AF0732935F139E667AC5566CF
46B9C8088192FC9036C4E451EB63BD36130A49C794944228BD4EB9170DA2FBE3
D026379848222D1E32800A1FF4268B9F5252A9D50F98819768BA54662F27979E
E7DEA596B815A23FE9265693965ED3B55819C343097E6A74D507E70ACEB7CC89
057F2C50576DE572AD575013FC83B2CC72B20DD65BAF2E792B3E5997B2AF2847
793F753122566FE30E1382B148725A4FEDFEEB79732608E2FBA78B498166AEB3
D65EA9B9F666FDDB4F12717A117BFF4ADA0E58B538F837CCE158DEF5E511BDA3
DF7B8A6F331D2600DB30E78326CB86D694C3680D34A9946677C7DB5658E33BED
94B9340286CF255AEA188B7977E2574A42F5DCDB4A73D1AA90B292F9CC850D40
5BDDB0B14A5E5FDBF032BBC444A05780D05E3A85BB195D59E7EDED08FCA49A0E
22ED0F15D3DD0EC5F3E5168D05CDA77145BBEA2E19F47F340576DE5C05E600BA
11C34DBD3891744A459746E270DD02897A2C6260F14390BC4389312EBD243785
81C3B3A2EB67E250F47105C3D3A05A5B4850109F98CD1E1FB97C46AABE31E5D7
227062060E9EF61354084EE810D83EDE3713E43052C746C27299C25812E2CF71
E6FBEB15752F91B526F228526DAE65030B719D7DCA210C72EDB98A7E4F05A18E
16B147126026C68A2A34479693B482DF4D6F2F825FF6252B088CF64E47B5DE1F
EB877CA1D189DF2AC550A35EE13A7553848B0E953F386885006AA474ED720346
A205AEF22655FF2F0E31C05985F51924EDD70E07314DC90246E10BC653244D56
B8B9F660F9094399063A64FE441533039417F461F38BC19E20121561D2EBA2FD
24566ECB7BC9128193C3D93B82E50BCD0C5BA9241960B683B81FE48262A646A7
022D78C7B2DFBE62DC97A1E5B6F7E373B2C90D91A484A98548928575C0AA2AC4
a192c2408a8a6754d8ab797515691e7c56c3c51279ca76dee6641e98f0d52e18
ED9304BBEA68784F4154DF8428F4A4CE65C3779565BA93F9A544B226F90CE4E2
766DBE048BAFE59ED79A4EAA6796402F3195DB2DC40EBD7768CD2A2B706F34DC
8343BA6D67B296C62A96661798313437201002FA4983FFA3BAB0BA42356CE9E6
A10E95215D860F76932D815EB2B2D12084A420BF9270AFD32FB4500429CBEA7A
981992203F5F33FA724FC82E1B8D15833FF3CE79A128E74A092D1AA34F8332F6
A69CD31857DFBE3FB138E5D5BB5EA0A1BBEB7204926BA17AD36FB0E6E3F50EF0
9AAE7B072324E0ADAFE111A618BB6DDFA6706CD53EAAE15D8A312688B052B2D3
3A587AE959CC00E7E61A0A87610599D90CF4571090FEE3ABABEAD46D275B6969
6CA8F057CAEFEB78116E58D96CC0DC2547BC226C3FD23BE48A9D6E452864A40F
57D660B0466E18D15DDA1634AC575A5007151DC5B8A1F3CB5DBF38AC996F0716
F3665EDE14437B2B0AA92651BCE403677E43BB2883F765E6FFFF6759E5D15AB8
B1DCC651AC4F168EE658285293119E47C95A79391C5AE560A977D63BF8518EF5
F34A8EDC534A8B73F73A9B2E5B169ECCE7774D00FCB64FCB89D899B468A961E3
The file names, so you can tell what you have. Their hashes are in the hash checker and in the downloadable archive.
Publishers take old builds offline without warning, so a link here can stop working even though the hash stays correct forever. If you already have the file, the hash is what matters: it tells you whether what you have is what they published.
Every Microsoft Edge version with a published manifest, newest first. The most recent ones are listed above with their file names and hashes.
Matched on the categories Microsoft Corporation and others declare in their own manifests, so the grouping is theirs rather than ours. Each one has its official URL and hash on the same terms as this page.
Not related to Microsoft Edge — just other entries, each with its own official URL and published hash.