Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsmage.exe is Microsoft’s Manifest Generation and Editing Tool, a command-line utility for creating, editing, signing and verifying ClickOnce application and deployment manifests. It is normally installed with Visual Studio or the Windows SDK. A copy supplied by either toolchain is legitimate developer software, but any unexpected file with that name should be checked before you run it. Missing-file errors usually mean the required Visual Studio or SDK component is not installed, or that you are using a normal Command Prompt instead of a Visual Studio developer shell.
What mage.exe does
Microsoft describes Mage.exe as “The Manifest Generation and Editing Tool (Mage.exe) is a command-line tool that supports the creation and editing of application and deployment manifests.” Those manifests are XML files used by ClickOnce, the Windows deployment technology that publishes and updates .NET applications.
As an Amazon Associate I earn from qualifying purchases.
Mage.exe can be called from batch scripts, Windows applications or a Visual Studio developer shell. Visual Studio documentation also identifies it as a ClickOnce tool distributed with the Windows SDK. The exact folder depends on the Visual Studio edition, installed workloads, SDK version and whether the machine has 32-bit or 64-bit components, so there is no single path that is correct for every computer.
Recommended Free Tools
Application and deployment manifests
A ClickOnce deployment normally has two related manifests. The deployment manifest tells ClickOnce where the application is published and which application version should be installed. The application manifest lists the files and assemblies that make up a particular version. Mage.exe can create or modify both types.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The tool’s documented operations include:
- -New: creates a new deployment or application manifest.
- -Update: changes an existing manifest.
- -Sign: adds or replaces a digital signature.
- -Verify: checks a signature. Microsoft documents this operation for .NET Framework 4.7 and later.
- -cc (ClearApplicationCache): clears the downloaded cache used by online-only ClickOnce applications.
The tool is not a Windows core process required for ordinary desktop use. If you never develop or package a ClickOnce application, you may never need to run it. Its presence is expected on a development workstation that has the relevant Microsoft toolchain installed.
Is mage.exe safe?
A mage.exe installed by Visual Studio or the Windows SDK is legitimate Microsoft developer tooling. That statement applies to the file supplied by those installations; it does not automatically validate every file named mage.exe anywhere on a disk. Malware can use a familiar filename, and a damaged or copied executable may not belong to the installed toolchain.
Check the file’s location
- In File Explorer, right-click the file and choose Properties.
- On the General tab, note the full path. A path under a known Visual Studio or Windows SDK installation is more plausible than a copy in a temporary folder, a user profile download directory or an unrelated application folder.
- Use the Details tab to inspect the product and company information. The wording should be consistent with Microsoft development tools.
Folder names alone are not proof. Visual Studio can be installed on a non-default drive, and an attacker can create a convincing-looking directory.
Inspect the digital signature
- Open the file’s Properties dialog and select Digital Signatures.
- Select the signer, choose Details, and confirm that Windows reports the signature as valid.
- Check that the signer is Microsoft and that the certificate has not expired or been revoked according to Windows’ validation result.
If the Digital Signatures tab is absent, the signature is invalid, or the publisher is not what you expect, do not execute the file. Keep the file isolated and scan it with your organization’s security software. The official documentation establishes what genuine Mage.exe does and where Microsoft distributes it; it does not certify an arbitrary copy discovered on a computer.
When a security warning is appropriate
- The file arrived in an email, archive, peer-to-peer download or an unofficial “DLL fixer” package.
- Its path is a temporary, cache or user-download location with no corresponding Visual Studio or SDK installation.
- The file requests elevated privileges unexpectedly or launches unrelated programs.
- The file has a mismatched product name, an invalid signature or a publisher other than Microsoft.
Do not replace a suspicious file with one downloaded from a random website. The safer remedy is to repair or add the Microsoft component that provides Mage.exe.
Why Windows says mage.exe is missing or not recognized
Most “mage.exe not found” and “’mage’ is not recognized” messages have one of these causes:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- Visual Studio is not installed, or its ClickOnce/.NET tooling was omitted.
- The Windows SDK is absent or its relevant developer tools were not selected.
- The executable exists, but the current shell’s
PATHdoes not include its directory. - You opened a regular Command Prompt or PowerShell window instead of a Visual Studio Developer Command Prompt or Developer PowerShell.
- The installation is damaged, partially removed or left behind after an upgrade.
- A script assumes a path from a different Visual Studio edition, architecture or machine.
Before changing anything, establish which toolchain your project expects. A build script written for a Visual Studio installation may not work merely because an SDK from another release is present.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fix a missing mage.exe step by step
1. Confirm whether Visual Studio or the Windows SDK is installed
Open Settings > Apps > Installed apps (or Apps & features on older Windows versions) and look for Visual Studio, a Visual Studio Installer entry or a Windows Software Development Kit. You can also check your organization’s standard developer-image documentation.
If neither distribution route is present, the missing executable is expected. Install the toolchain required by your project rather than copying a standalone file. If the machine belongs to an employer or school, follow its approved software process and select the same release used by the project.
2. Add or repair the Visual Studio components
- Start Visual Studio Installer.
- Find the installed Visual Studio entry and choose Modify. If the installation is malfunctioning, choose More > Repair instead.
- Review the installed workloads and individual components related to .NET desktop development, ClickOnce publishing and the Windows SDK. Component names can differ by Visual Studio release, so select the ClickOnce and SDK items offered for your version.
- Apply the change and allow the installer to complete. Restart Windows if the installer requests it.
Repairing restores files registered by the installer; it does not repair a project’s invalid manifest, certificate or publication settings. Those problems require the manifest steps later in this guide.
3. Add or repair the Windows SDK route
If your build documentation specifies the Windows SDK, use the Visual Studio Installer or the SDK installer approved for your Windows and Visual Studio version. Select the developer tools required by the project. A system can have several SDK releases, and installing a newer one does not guarantee that an older build script will find the same path.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
After installation, avoid hard-coding a guessed directory. Open the developer shell associated with the toolchain instead.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
4. Use the correct developer shell
- Open the Start menu and search for Developer Command Prompt for Visual Studio or Developer PowerShell for Visual Studio.
- Choose the entry that matches the Visual Studio installation used by the project.
- Run
mage. If the command is available, the shell has placed the intended tool directory onPATH.
In a normal Command Prompt, mage may fail even though the executable is installed. That is a path configuration issue, not proof that the file is missing. For repeatable builds, invoke the appropriate developer-shell setup before the build script, or use the fully qualified path discovered by that shell. Do not permanently add a random copy to the system path just to silence one error.
5. Use MageUI.exe when a graphical workflow is preferable
Microsoft says MageUI.exe supports the same core functionality and is installed with Visual Studio. Search the Start menu for MageUI or launch it from the Visual Studio developer environment. It can be useful when you need to inspect manifest fields, select files and certificates interactively, or diagnose a path mistake without composing a long command line.
MageUI does not make an invalid certificate valid and does not remove the need to rebuild hashes after files change. It is an alternative interface to the same manifest work.
Fix manifest path and creation errors
Check every file path
When a command references an application manifest with -AppManifest, the named file must exist and must actually be an application manifest. Mage.exe reports an error if the path is wrong or the file is a different XML document. Check spelling, drive letters, relative-path assumptions and quoting around paths that contain spaces.
- Run the command from the directory your script expects, or use absolute paths while diagnosing it.
- Confirm that the file is not a deployment manifest when the operation requires an application manifest.
- Check that the build has completed before Mage.exe runs; a failed build may never produce the expected manifest.
- Use the same account and environment as the failing build. A path visible to an interactive user may not be visible to a service or continuous-integration agent.
Create a new manifest with -New
Use -New when no suitable deployment or application manifest exists. Select the manifest type required by the ClickOnce publication process, supply the project’s identity and version values, and save the result in the location expected by the next build step. Keep deployment and application manifests distinct; pointing a later command at the wrong type produces confusing errors.
Because Mage.exe is a command-line tool, preserve the exact command and working directory in your build log. If a GUI is used to create the file, record the resulting paths and version values so a later automated build does not silently target a different manifest.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Modify an existing manifest with -Update
Use -Update when the manifest already exists and you need to refresh its metadata or file list. Verify that the input file is the intended version before updating it. Updating the wrong copy can produce a validly formatted manifest that still points ClickOnce at stale content.
Repair file-hash and “changed file” errors
ClickOnce uses hashes in an application manifest to detect changes to assemblies and other files. Microsoft documents -FromDirectory as the option that populates an application manifest with the files in a directory and generates the hashes used for tamper detection.
If you edit, replace, add or remove deployment content after the manifest was generated, the old hashes no longer describe the directory. Re-run the update using the correct directory, confirm that the resulting file list is complete, and then sign the changed manifest again. A common failure pattern is to copy a new DLL into the publish folder while continuing to serve an application manifest generated from the previous build.
- Stop publishing the affected version while you correct it.
- Identify the exact directory that should be deployed.
- Use
-Updatewith the appropriate source directory, including-FromDirectorywhere the workflow requires Mage.exe to rebuild the file list and hashes. - Check that every expected assembly and content file appears in the application manifest.
- Sign the final manifest after all content changes are complete.
Repair signing and verification errors
Sign only after edits are finished
Signing is normally the last manifest operation. Microsoft explains why: the signature contains a hash of the file. If you update a signed file, the changed bytes invalidate that hash and the signature block is removed. Therefore, a workflow that signs first and updates later will end with an unsigned or invalidly signed manifest.
Use -Sign with the X.509 certificate or key container required by your organization. Protect the private key, use the certificate intended for the deployment identity and make sure the publishing process can access it. If the certificate is missing, expired or inaccessible, Mage.exe cannot produce a usable signature even when the manifest itself is correct.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Verify the result
Where supported, use -Verify to check the signature after signing. Microsoft documents this operation for .NET Framework 4.7 and later. On an older framework or tool environment, the option may not be available as documented, so check the installed framework and Mage.exe version before treating a verification failure as a certificate failure.
A successful verification confirms the signature check for that file; it does not prove that the deployment URL, version, file list or application code is correct. Test installation and update behavior separately.
Fix ClickOnce deployments that do not refresh
If a deployment installs but does not offer a new version, inspect the deployment manifest’s provider URL and its reference to the application manifest. Confirm that the URL is reachable from the client network, that the application-manifest reference points to the published file, and that the deployment and application version values were incremented consistently.
- Compare the URL in the deployment manifest with the location where the provider actually publishes updates.
- Check that the deployment manifest references the intended application-manifest filename, not an older build or a local development path.
- Confirm that the version values identify the new release and that the server is returning the updated files rather than a cached response.
- After correcting the publication, test from a clean client or clear the local ClickOnce cache when an online-only application is stuck on stale data.
Mage.exe documents -cc, also called ClearApplicationCache, for clearing the downloaded cache of online-only applications. Use it deliberately: clearing the cache removes locally downloaded ClickOnce data and can require the application to download again. It does not repair a wrong provider URL or a badly signed manifest; those must be fixed at the publication source.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Choose the right fix for the symptom
| Symptom | Likely cause | First action |
|---|---|---|
mage is not recognized |
Missing Visual Studio/SDK component or a shell without the tool on PATH |
Open the matching Developer Command Prompt, then repair or add the component if the command is still unavailable. |
| Application-manifest path error | The -AppManifest path is wrong or names the wrong manifest type |
Confirm the file exists, is an application manifest and is accessible from the current working directory. |
| Files fail validation after a rebuild | Hashes describe an older publish directory | Regenerate the file list and hashes with the correct directory, then sign again. |
| Signature becomes invalid after an edit | An update changed bytes covered by the signature | Complete all updates first and run -Sign as the final step; use -Verify where supported. |
| ClickOnce keeps offering an old version | Stale provider URL, manifest reference, version value or local cache | Inspect publication metadata, then consider -cc for an online-only client that retains stale downloaded data. |
| Unexpected mage.exe copy | Unknown provenance or a file unrelated to the Microsoft toolchain | Do not run it; check its signature and location and obtain the tool through Visual Studio or the Windows SDK. |
Practical checks before rerunning a build
- Record the Visual Studio edition, SDK release and .NET Framework version used by the build.
- Use the matching Developer Command Prompt or Developer PowerShell.
- Confirm that the application and deployment manifests are the intended files for this build.
- Check every path, especially paths supplied through environment variables or relative to the working directory.
- Regenerate hashes whenever deployment content changes.
- Sign after the final update, never before.
- Run signature verification where the installed framework and Mage.exe support
-Verify. - For update failures, inspect provider URLs, manifest references and version values before clearing any cache.
- Keep private signing keys protected and out of source-control repositories.
When reinstalling is not the answer
Reinstalling Visual Studio or the SDK can restore a missing executable, but it will not correct a malformed manifest, an incorrect URL, stale hashes or an invalid certificate. Conversely, repeatedly editing a manifest is wasted effort if Mage.exe itself is absent or the shell cannot locate it. Separate the problem into provenance, executable availability, manifest content, signing and ClickOnce caching; each category has a different remedy.
There is no reliable published statistic establishing how often mage.exe errors occur, how often a file with that name is malicious, or how frequently a particular repair succeeds. Treat the diagnosis above as a decision process based on the observed symptom and the documented behavior of the Microsoft tool.
If you prefer an automated Windows-maintenance shortcut after trying the manual checks, Outbyte PC Repair can address more than 100 common Windows issues, including broken system elements, invalid redirects and shared DLL problems; it also offers settings adjustments, temporary and cache cleanup, privacy tools, vulnerability checks, a real-time boost, file shredding and an app-crash log. It runs on Windows 11, 10, 8 and 7 and has a free trial by category for at least two days before a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Bottom line
Use Mage.exe only when your ClickOnce workflow requires it, and obtain it through the Visual Studio or Windows SDK toolchain. For a missing command, repair or add the correct component and use the matching developer shell. For manifest errors, correct paths and manifest types; rebuild hashes after content changes; sign last; verify where supported; and investigate provider metadata or clear the online-only cache only when an update remains stale.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
