Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For the documented Configuration Manager console deployment case, the immediate fix is to replace curly (“smart”) quotation marks around TargetDir with ordinary ASCII double quotes. Use 0x80070057 as a starting clue, not a complete diagnosis: it means E_INVALIDARG (“The parameter is incorrect”), and AppEnforce.log shows which command or deployment stage actually failed.
Quick fix: correct the installation command
Edit the deployment type’s installation program and manually retype both quotation marks. Do not paste them from a formatted document or web page.
| Incorrect | Correct |
|---|---|
ConsoleSetup.exe /q TargetDir=”%ProgramFiles%ConfigMgr Console” DefaultSiteServerName=cm01.contoso.com |
ConsoleSetup.exe /q TargetDir="%ProgramFiles%ConfigMgr Console" DefaultSiteServerName=cm01.contoso.com |
The corrected pattern is:
ConsoleSetup.exe /q TargetDir="%ProgramFiles%ConfigMgr Console" DefaultSiteServerName=SERVER-FQDNReplace SERVER-FQDN with the intended site-server fully qualified domain name. The matching reported case was resolved by changing Unicode curly quotes to U+0022 ASCII quotes; see the original case report at Prajwal Desai’s forum. This is a confirmed fix for that command-line error, not a universal cure for every occurrence of the HRESULT.
Recommended Free Tools
What 0x80070057 (-2147024809) means
These values identify the same Windows error:
0x80070057-2147024809E_INVALIDARG- “The parameter is incorrect”
The code does not identify the bad parameter. In Configuration Manager (still commonly called SCCM), Software Center may show only the enforcement result while the useful evidence appears immediately beforehand in the client logs. Microsoft documents the code in several Configuration Manager contexts, so do not assume it proves that ConsoleSetup.exe itself rejected the command: Microsoft’s Configuration Manager update notes and this Microsoft error explanation illustrate its generic nature.
#1 Best Overall
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
Why quotation marks can break ConsoleSetup.exe
The console installer parses options such as /q, TargetDir, and DefaultSiteServerName. A curly opening or closing quote is a different Unicode character from "; it can be passed literally instead of delimiting a path. A path containing spaces then becomes malformed, and setup can fail almost immediately with E_INVALIDARG.
Other character and syntax problems deserve the same check:
- Missing or mismatched closing quotes.
- Extra quotation marks inserted by a packaging system.
- En dashes or em dashes substituted for hyphens.
- Non-breaking spaces, invisible Unicode characters, or copied line breaks.
- A misspelled option, empty
DefaultSiteServerName, or invalidTargetDir.
Repair the deployment type
- Open the application and its deployment type in the Configuration Manager console.
- Review the complete installation program shown in the deployment type. Retype the quote characters directly in the console so both are ASCII
". - Ensure
ConsoleSetup.exeand every setup file it needs are in the application content source. Use a deterministic local or content-cache path where appropriate. - Save the revision and redistribute content if the source or application revision changed.
- Trigger policy retrieval on a test client, then retry the deployment.
Check the command syntax against the version of the console package being deployed. Options and supported behavior are not guaranteed to be identical across every Configuration Manager branch.
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 →Test outside Software Center, then as Local System
Elevated administrator test
From an elevated command prompt opened in the directory containing the installer, run the exact command:
Rank #2
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
ConsoleSetup.exe /q TargetDir="%ProgramFiles%ConfigMgr Console" DefaultSiteServerName=cm01.contoso.comConfirm that setup returns success, installs to the intended directory, creates the expected shortcut, and opens with the correct site-server configuration.
Local System test
A manual administrator test does not reproduce a device deployment that runs as Local System. Microsoft recommends reproducing the installation in that context; its application-install guidance is at the Configuration Manager application-install error reference.
Using an approved copy of Microsoft Sysinternals PsExec, open an interactive SYSTEM prompt:
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 →psexec -accepteula -s -i cmd
whoamiThe expected identity is:
nt authoritysystemRun the same command there. A failure under SYSTEM points to the command, installer, prerequisites, permissions, content, or machine context—not to the Software Center interface.
Rank #3
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Read the right logs
Application enforcement
Start with:
C:WindowsCCMLogsAppEnforce.logFind the command immediately before the failure and search for ConsoleSetup.exe, EnforceApp, CommenceEnforcement, 0x80070057, the installer exit code, and detection results. The logged command is more valuable than the shortened Software Center message.
Discovery and content acquisition
AppDiscovery.log: applicability and detection evaluation.CAS.log: client cache and content-location activity.ContentTransferManager.logandDataTransferService.log: download and transfer failures.LocationServices.log: boundary, boundary-group, and distribution-point location.
If AppEnforce.log never shows the installer launching, investigate content acquisition instead. A similar HRESULT in ContentTransferManager.log can involve a distribution point or alternate content provider; Microsoft describes these cases in its Configuration Manager change summary.
Deployment settings that prevent misleading failures
Installation behavior and logon requirement
For a console intended for everyone using a managed device, choose Install for system and avoid requiring a logged-on user. A deliberate per-user deployment is possible, but test profile paths, permissions, detection, and availability for that design.
Content execution
Download content from distribution point and run locally usually gives the most predictable execution: setup runs from the client cache rather than depending on a live UNC path. Verify content distribution, boundary membership, and distribution-point availability before troubleshooting setup syntax.
Rank #4
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Detection, requirements, and return codes
- Detect the installed console (a known file and version, registry value, or uninstall entry), not the source
ConsoleSetup.exe. - Match requirements and dependencies to the Windows and Configuration Manager environment supported by the packaged console version.
- Configure documented success and reboot return codes appropriately.
A successful installation that remains offered in Software Center usually indicates detection, architecture/registry-view, stale policy, or an uninstall/reinstall loop rather than another installer-quote problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the corrected command still fails
Verify the site-server argument
Check spelling, DNS resolution, reachability from the client, and whether the FQDN identifies the intended site system. A short name may work in some environments, but use the FQDN shown in your supported console-install syntax unless your package documentation says otherwise.
Separate enforcement from a task sequence
In a task sequence, an Install Application step can surface a generic top-level failure even when policy, applicability, dependency, content, or enforcement caused it. Trace smsts.log together with the component log; Microsoft’s procedure is documented at Troubleshoot the Install Application step.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTrace deeper when logs are insufficient
Microsoft Sysinternals Process Monitor can reveal file, registry, and process-access failures. PsExec and Process Monitor are free utilities. For a failure affecting multiple clients or suggesting an unsupported product or infrastructure condition, use Microsoft Support.
Best Value
- Video Link to instructions and Free support VIA Amazon
- 24/7 Tech Support!
- key code included
Validation checklist
- The command in
AppEnforce.logcontains only straight ASCII quotes. ConsoleSetup.exelaunches from available local content.- The console installs in the expected directory and opens.
- The configured site server resolves and is reachable.
- The detection method reports the installed version.
- Software Center reports success without repeatedly reinstalling.
- The same command behaves as Local System when the deployment uses device context.
Frequently Asked Questions
Is 0x80070057 specific to SCCM?
No. It is the generic Windows E_INVALIDARG code, meaning an argument or parameter was invalid. The relevant Configuration Manager log determines whether the fault is command parsing, content, detection, or another layer.
Do I need to reinstall the Configuration Manager client?
Not as a first response. Inspect the exact command in AppEnforce.log and test it under the deployment context before considering client repair.
Where is AppEnforce.log?
On a standard Windows client, it is at C:WindowsCCMLogsAppEnforce.log.
What if the code appears only in ContentTransferManager.log?
Treat it as a content-location or transfer investigation: check distribution, boundaries, the selected distribution point, and alternate content providers rather than changing ConsoleSetup.exe first.
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.
