Audit mode overview
When Windows boots, it starts in either Out-Of-Box Experience (OOBE) mode or in Audit mode:
- OOBE is the default out-of-box experience that allows end users to enter their account information, select language, accept the Microsoft Terms of Service, and set up networking.
- Audit mode allows you to make additional changes to the Windows installation before you send the computer to a customer or capture the image for reuse in your organization. You can install drivers included in a driver package, install applications, or make other updates that require the Windows installation to be running.
Audit mode account
When you boot to Audit mode, you log into the system using the built-in administrator account. After you log on to the system, the built-in administrator account is immediately disabled during the auditUser configuration pass. The next time that the computer reboots, the built-in administrator account remains disabled. For more information, see Enable and Disable the Built-in Administrator Account.
- If you're in Audit mode and a password-protected screen saver starts, you can't log back on to the system. The built-in administrator account that's used to log on to Audit mode is immediately disabled after logon. Disable the screen saver by either changing the power plan in the Settings app, or configure and deploy a custom plan. For more information, see Create a Custom Power Plan.
- Settings in an unattended answer file from the oobeSystem configuration pass do not appear in Audit mode.
- If you're running scripts, installers, and diagnostic tools in Audit mode on an S mode image, you may have to enable manufacturing mode. See Manufacturing mode for details.
Benefits of using Audit mode
In Audit mode, you can:
Bypass OOBE. You can access the desktop as quickly as possible. You do not have to configure default settings such as a user account, location, and time zone.
Install applications, add device drivers, and run scripts. You can connect to a network and access additional installation files and scripts. You can also install additional language packs and device drivers. For more information, see Add a Driver Online in Audit mode.
Add more customizations to a reference image. This reduces the number of images that you have to manage. For example, you can create a single reference image that contains the basic customizations that you want to apply to all Windows images. You can then boot the reference image to Audit mode and make additional changes that are specific to the computer. These changes can be customer-requested applications or specific device drivers.
You shouldn't use Audit mode for testing and validation scenarios.
- For Hardware and driver testing, you can use Microsoft Validation OS.
- To test OS functionality, don't use Audit mode. Only test on an OS that has completed the OOBE process.
Boot to Audit mode
You can boot to Audit mode on a new or existing Windows installation. For more information, see Boot Windows to Audit mode or OOBE.
- Understanding Servicing Strategies
- Windows Setup Configuration Passes
- How Configuration Passes Work
- Windows Setup Scenarios and Best Practices
- Windows Setup Installation Process
- Windows Setup Automation Overview
- Windows Setup Supported Platforms and Cross-Platform Deployments
- Windows 10 S manufacturing mode