Download Standard SATA AHCI Controller Drivers Windows 10 All the storage drivers (Hard Disk) connected to your computer require a SATA AHCI Controller Driver. Without these drivers installed in Windows 10, you will start having issues while accessing the drives of your PC. Most standard driver routines and some of the configuration-dependent objects they use are defined by the I/O manager. The ISR, SynchCritSection routine, and those shown in the Driver Object figure with names containing the word 'custom' are defined by the NT kernel.
For a Microsoft Windows 2000 version of this article, see
268852.
IN THIS TASK
Summary
This step-by-step article describes how to force Windows to use a standard VGA mode driver that is included with Windows. This procedure is useful in the following scenario.
If you install Windows on a computer that is using an unsupported video adapter, Windows Setup installs a standard VGA mode driver. However, after you install Windows, you obtain and install a Windows-compatible driver for your video adapter from an original equipment manufacturer (OEM).
In this scenario, the computer may have problems shutting down, or the computer may stop responding (hang). To troubleshoot this problem, you may want remove the new OEM drivers and revert to the standard VGA drivers to determine whether the OEM drivers cause the problem.
This article describes how to remove OEM video drivers and force Windows to use the standard VGA drivers that are included with Windows.
Force Windows to Use the Standard VGA Mode Drivers Without Having to Use Safe Mode
When you install an OEM driver, the Windows installer program copies the OEM installation file (Oemsetup.inf) to the %Systemroot%Inf folder. Setup then renames the Oemsetup.inf file to Oemn.inf, where n is an incremental number for each OEM driver that is installed.
To identify the OEM video-specific Oemn.inf file, you can open each Oemn.inf file in Microsoft Notepad, and then compare it with the original Oemsetup.inf file. After you find a match, move that specific Oemn.inf and Oemn.pnf files to a different location, or rename the files with a different file name extension.
After you locate the matching .inf files, move the Oemn.inf and Oemn.pnf to a different folder.
In Device Manager, right-click your video adapter, and then click Uninstall to remove the video adapter.
Restart your computer.
After you log on, you receive a message stating that new hardware has been found and that it is a VGA compatible video controller. The Found New Hardware Wizard starts.Click Next.
Click Search for suitable driver, and then click Next.
Click to clear all of the search option check boxes, and then click Next.
Click Disable the device, and then click Finish.
After you finish steps 1 through 7, Windows uses the Vga.sys generic video driver. This is the same VGA driver that Windows uses in Safe mode.
If the computer becomes stable or shuts down in a typical manner while you are using the standard VGA driver, you may have to contact the OEM driver vendor to report the problems that you have when you use the OEM driver. You may also have to obtain and install a newer driver (if one is available) that resolves these problems.
To restore the OEM drivers, follow these steps:
Move the Oemn.inf and Oemn.pnf files back to the %Systemroot%Inf folder.
Use Device Manager to remove the VGA video adapter, and then restart the computer.
Windows Plug and Play locates the OEM video adapter and reinstalls the OEM drivers automatically.
Standard Driver Lie Angle
NOTE: If you press F8, and then click Enable VGA Mode on the Windows Startup menu, Windows starts with a screen area of 640 by 480 pixels with low 8-bit color and may use an OEM video driver, not the standard VGA driver.
Versions supported
- Windows 10
- Windows 8.1
Standard Driver Length Men
Applies to
- Device manufacturers of CDC Control devices
Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.
- Improved PnP and power management by the driver (such as, handling surprise removal).
- Added power management features such as USB Selective Suspend.
In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Usbser.sys installation
Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
Note
If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.
Windows 10
In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.
USBClass_02
USBClass_02&SubClass_02
- If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
- If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
- If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.
Note
Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.
Windows 8.1 and earlier versions
In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.
The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.
For more information, see this KB article.
Configure selective suspend for Usbser.sys
Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:
To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:
'0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.
'0x00000000': Enters selective suspend only when there are no open handles to the device.
That entry can be added in one of two ways:
Write an INF that references the install INF and add the registry entry in the HW.AddReg section.
Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.
For more information, see Microsoft OS Descriptors.
Develop Windows applications for a USB CDC device
If you install Usbser.sys for the USB CDC device, here are the application programming model options:
Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.
In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:
Win32 programming model:
.NET framework programming model:
Related topics