Overview
The Setup application programming interface (API) provides a set of functions that your setup application can call to perform installation operations. These setup functions work with Windows INF files to provide the following setup functionality.
| For information about | See |
|---|---|
| Queuing files | File Queues |
| Installing files | File Queues Setup Applications Creating Setup Applications |
| Handling errors and prompting for media | Disk Prompting and Error Handling |
| Updating registry entries | Setup Applications |
| Logging installed files | File Log |
| Storing the most recently used source paths | MRU Source List |
Unicode and ANSI versions are available for most setup functions. Unicode text files should contain the standard 0xFEFF byte-order mark to enable setup functions to identify the file as Unicode text.
Although the Setup API supports prompting for new media and basic error-handling dialog boxes, the setup functions do not provide wizard functionality or a generic user interface.
Developers should consider whether they can use Windows Installer to install their applications rather than the Setup API. Windows Installer reduces the total cost of ownership (TCO) for your customers by enabling them to efficiently install and configure your products and applications. The installer can also provide your product with new capabilities to advertise features without installing them, to install products on-demand, and to add user customizations.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for