| Previous | Next |
| SPAPI_E_DI_DO_DEFAULT | SPAPI_E_INVALID_HWPROFILE |
SPAPI_E_DI_NOFILECOPY
No file copy can be a successful installation outcome
SPAPI_E_DI_NOFILECOPY indicates that the current device installation operation does not need file-copy work. It is associated with the DIF and file-queue control path rather than evidence that a source file is missing. Existing files, a null-driver installation, or an installer phase that only updates configuration can legitimately produce this result.
The meaning must be evaluated together with SP_DEVINSTALL_PARAMS. Flags such as DI_NOFILECOPY and DI_NOVCP determine whether installers enqueue operations, use a caller-supplied queue, or commit file changes themselves.
Do not turn a qualified status into a copy error
- Inspect the active DIF code and device-installation flags.
- Check whether another phase already committed the required file queue.
- Separate “nothing to copy” from an empty queue caused by an incorrectly selected INF section.
- Use SetupAPI text logging to confirm which DDInstall sections and file operations were evaluated.
References
- Microsoft: SP_DEVINSTALL_PARAMS flags
- Microsoft: DIF_INSTALLDEVICEFILES
- Microsoft: SetupAPI error codes
Looking for a different code? Search another status or error code.