32-bit
exedownload.microsoft.com · publisher domain- File name
- NDP481-DevPack-ENU.exe
- SHA-256
- fd9ae4b63cbc8f7637249c4b29d25281b1f70fbe6d650109dcbf2bdf596cf994
- Silent install
- /install /quiet /norestart
by Microsoft Corporation · Proprietary
A technology that supports building and running Windows apps and web services.
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 "NDP481-DevPack-ENU.exe" -Algorithm SHA256macOS · Linux
shasum -a 256 "NDP481-DevPack-ENU.exe"Expected output
fd9ae4b63cbc8f7637249c4b29d25281b1f70fbe6d650109dcbf2bdf596cf994
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.
The unattended switch below is the one Microsoft Corporation declares in the installer manifest, not one we guessed by trying flags.
32-bit · publisher-declared
.\NDP481-DevPack-ENU.exe /install /quiet /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.
| Signal | Finding | Points |
|---|---|---|
| SHA-256 hash published | 4 of 4 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 | 4 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 | 4 of 4 over HTTPSAn installer fetched over plain HTTP can be modified in transit. | 15 / 15 |
| Release recency | last release about 49 months agoSoftware that has not shipped in years accumulates unpatched vulnerabilities. | 0 / 15 |
| Licence declared | ProprietaryA declared licence tells you what you are actually allowed to do with the software. | 5 / 5 |
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 4 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 85/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.DotNet.Framework.DeveloperPack_4 --exactUpgrade later
winget upgrade --id Microsoft.DotNet.Framework.DeveloperPack_4Why --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 .NET Framework Developer Pack, 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.
3B375FD01759808843D9D48CB1F2DD50711A14638C03387155471B10D98B6B30
878FDF9F137B1466855DE995C793B466CD50FCCC523D1F41250567973623180C
A70B790DCF7EE4A0CAE65FB82A16FB67FE970EB21B9424C9DA35E1ACAFBC4348
EFE311D8EA6A597860AF8549B184D837DA79B41F2C2C73D3EBE7386F2635544F
5D1399EABD7B11FAAA8498C9C9112ECDC30DE77B0F427C5FFBCC9A1A426A2F8F
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 .NET Framework Developer Pack 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 .NET Framework Developer Pack — just other entries, each with its own official URL and published hash.