| Previous | Next |
| ERROR_CANNOT_OPEN_PROFILE | ERROR_NOT_CONTAINER |
ERROR_BAD_PROFILE
WNetAddConnection2 lists ERROR_BAD_PROFILE as an incorrect user-profile format. The diagnostic boundary is local profile data used for remembered network mappings, not the syntax of the remote UNC path itself.
Compare persistent and temporary connection behavior. If a connection succeeds without CONNECT_UPDATE_PROFILE but fails when persistent state is read or updated, the network provider and remote resource may be healthy while the remembered-connection profile is damaged. Preserve the affected user context before deleting entries so the malformed state can be identified.
Confirm profile-specific failure
- Reproduce under the same user profile and logon session.
- Compare a temporary connection with a persistent redirected-device connection.
- Inventory remembered mappings and look for malformed or conflicting entries.
- Back up relevant profile state before cleanup so the original corruption is not destroyed.
WNetAddConnection2 · Retrieving WNet network errors
Looking for a different code? Search another status or error code.