| Previous | Next |
| MF_S_ASF_PARSEINPROGRESS | MQ_INFORMATION_PROPERTY |
MF_I_MANUAL_PROXY
Where the result originates
MF_I_MANUAL_PROXY means a network source has selected explicit proxy configuration rather than automatic discovery.
The result comes from the Media Foundation proxy locator used while resolving a source URL. A representative case is an application deliberately supplies a proxy property store and the locator reports that manual mode is active.
Evidence that survives retries
| Observation | What to capture |
|---|---|
| Primary discriminator | the source URL, proxy host and port, bypass list, authentication mode, and the property store passed to source resolution |
| Owning object | the Media Foundation proxy locator used while resolving a source URL, including its object identity and generation |
| Timeline marker | the call immediately before a network source has selected explicit proxy configuration rather than automatic discovery and the completion event, callback, or state change that followed |
| Comparison artifact | one known-good run that changes only this condition: repeat resolution once with the documented manual proxy values and once with the same URL under automatic proxy discovery |
A network source has selected explicit proxy configuration rather than automatic discovery. Preserve the original Media Foundation proxy locator used while resolving a source URL and the first result in the chain: a later UI message can replace this precise code with a generic playback, setup, network, or device failure.
A controlled verification sequence
- Record this result,
0x400D4272, the returning method, process architecture, Windows build, and component version. - Capture the source URL, proxy host and port, bypass list, authentication mode, and the property store passed to source resolution before retry logic changes the object.
- Perform this narrow comparison: repeat resolution once with the documented manual proxy values and once with the same URL under automatic proxy discovery.
What the result does not prove
In this case, an actual connection failure occurs later and returns a network or proxy HRESULT.
Nearby results that mean something else
| Result | Different condition |
|---|---|
MF_E_UNEXPECTED | An unexpected error has occurred in the operation requested. |
MF_E_INVALIDNAME | Invalid name. |
MF_E_INVALIDTYPE | Invalid type. |
Repair at the owning layer
The supported corrective direction is to correct the explicit proxy endpoint or bypass rule; do not treat this informational result as a transport failure by itself.
For an incident, keep the symbolic constant together with 0x400D4272.
Technical references
Looking for a different code? Search another status or error code.