Ctp Pro 1.8 Serial

This section of the documentation provides specifications for hardware compatibility for systems running Windows 10, version 1703. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • System.Client.BluetoothController.Base These requirements apply to systems that have generic Bluetooth controllers. System.Client.BluetoothController.Base.4LeSpecification If a system includes a Bluetooth enabled controller it must support the Bluetooth 4.0 specification requirements. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description The Bluetooth enabled controller must comply with the Basic Rate (BR) and Low Energy (LE) Combined Core Configuration Controller Parts and Host/Controller Interface (HCI) Core Configuration requirements outlined in the Compliance Bluetooth Version 4.0 specifications. System.Client.BluetoothController.Base.CS *Systems that support Connected Standby with Bluetooth enabled controllers must ship with Microsoft's inbox Bluetooth stack and support the MSFT Defined HCI extensions support for hardware offload of advertisement and RSSI monitoring (see System.Client.BluetoothController.Base.HciExtensions). * Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Systems that support Connected Standby that ship with Bluetooth enabled controllers must ship with Microsoft's inbox Bluetooth stack. System.Client.BluetoothController.Base.HciExtensions MSFT Defined HCI extensions support for hardware offload of advertisement and RSSI monitoring.

Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Terms: If-Implemented Description Radios that support the Microsoft-OSG Defined Bluetooth HCI Extensions must comply with the specification and pass the related HLKWLK tests. The details of the specifications will be shared at a later date.

View and Download Clevo W510LU service manual online. W510LU Laptop pdf manual download.

Partners will be notified via Connect. System.Client.BluetoothController.Base.LEStateCombinations Systems with Bluetooth enabled controllers must support a minimum set of LE state combinations.

Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description The Bluetooth enabled controller must allow the spec LE state combinations (as allowed in section [Vol 6] Part B, Section 1.1.1 of the Bluetooth version 4.0 spec). System.Client.BluetoothController.Base.LEWhiteList Systems with Bluetooth enabled controllers must support a minimum LE allow list size of 25 entries. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description The Bluetooth enabled controller on the system must support a minimum of 25 entries in its allow list for remote Low Energy (LE) devices. System.Client.BluetoothController.Base.NoBluetoothLEFilterDriver Bluetooth LE filter drivers are not allowed to load on BTHLEENUM.SYS.

Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description To ensure a uniform experience across Microsoft Store Apps using the Bluetooth LE (GATT) WinRT API, filter drivers shall not be loaded on BTHLEENUM.SYS. System.Client.BluetoothController.Base.OnOffStateControllableViaSoftware Bluetooth enabled controllers’ On/Off state must be controllable via software. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description When turning the radio off, Bluetooth enabled controllers shall be powered down to its lowest supported power state and no transmission/reception shall take place. Windows will terminate Bluetooth activity by unloading the inbox protocol drivers and their children, submitting the HCI_Reset command to the controller, and then setting the controller to the D3 logical power state, allowing bus drivers to power down the radio as appropriate. The radio can be completely powered off if a bus-supported method is available to turn the radio back on. No additional vendor software control components will be supported. On turning the radio back on, the Bluetooth stack for Windows shall resume the device to D0, allowing bus drivers to restart the device.

The Windows Bluetooth stack shall then reinitialize the Bluetooth enabled components of the controller. Bluetooth Radio Management shall only be enabled for internal Bluetooth 4.0 enabled controllers.

The on/off state of Bluetooth-enabled controllers shall be controllable via software as described in Bluetooth Software Radio Switch. The Off state is defined, at a minimum, as disabling the antenna component of the Bluetooth enabled module so there can be no transmission/reception. There must not be any hardware-only switches to control power to the Bluetooth enabled radio. The radio must maintain on/off state across sleep and reboot. System.Client.BluetoothController.Base.SimultaneousBrEdrAndLeTraffic Bluetooth enabled controllers must support simultaneous BR/EDR and LE traffic. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Bluetooth enabled controllers must allow the simultaneous use of both Basic Rate (BR)/Enhanced Data Rate (EDR) and Low Energy (LE) radios. System.Client.BluetoothController.Base.WidebandSpeech Applies to Windows 10 Mobile ARM Windows 10 Mobile x86 Description Wideband speech enables high definition voice quality (audio is sampled at 16 KHz as opposed to only 8 KHz) for telephony audio on Windows devices when the user is communicating via a Bluetooth peripheral that also supports wideband speech.

What this means is that Bluetooth radios must support wideband speech in the hardware as defined by the Bluetooth SIG and the which is included in the Bluetooth specification. At a minimum it must use at least one Bluetooth SIG defined wideband speech codec (currently mSBC). Business Justification: We want users to experience the best possible quality audio when using Bluetooth peripherals on Windows. Wideband speech is becoming a standard for peripherals that support the HFP profile. Our competition already supports it.

System.Client.BluetoothController.Base.WLANBTCoexistence Windows Systems that support both WLAN and Bluetooth must meet WLAN-BT Co-existence requirements. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Windows systems that support both WLAN and Bluetooth must meet WLAN-BT Co-existence requirements listed below. The requirement is applicable to all WLAN devices across all bus types. • Must not drop the connection with WLAN AP when Bluetooth is scanning for new devices. • Must be able to scan simultaneously for both WLAN and Bluetooth networks. System.Client.BluetoothController.NonUSB These requirements apply to systems that have non-USB Bluetooth enabled controllers.

System.Client.BluetoothController.NonUSB.NonUsbUsesMicrosoftsStack Any platform using a non-USB connected Bluetooth enabled controller must ship with Microsoft’s inbox Bluetooth stack. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Any platform using a non-USB connected Bluetooth enabled controller must ship with Microsoft’s inbox Bluetooth stack. System.Client.BluetoothController.NonUSB.ScoSupport Any platform with a non-USB connected Bluetooth enabled controller must use a sideband channel for SCO. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Any platform using a Non-USB connected Bluetooth enabled controller must use sideband channel for SCO (such as SCO over an I2S/PCM interface).

System.Client.BluetoothController.USB These requirements apply to systems that have USB Bluetooth enabled controllers. System.Client.BluetoothController.USB.ScoDataTransportLayer Bluetooth enabled host controllers support the SCO data transport layer as specified in the Bluetooth 2.1+EDR specifications. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description A System with a Bluetooth enabled controller must comply with the Synchronous Connection Oriented (SCO)-USB requirements that are outlined in the Specification of the Bluetooth System, Version 2.1 + Enhanced Data Rate (EDR), Part A, Section 3.5. System.Client.BrightnessControls This section describes requirements systems with brightness controls.

System.Client.BrightnessControls.BacklightOptimization Windows Display Driver Model ( WDDM) 1.2 drivers must enable scenario based backlight power optimization to reduce backlight level used by integrated panel. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Windows Server 2016 x64 Description • If WDDM driver supports scenario based backlight power optimization, it must indicate the support by implementing the DXGK_BRIGHTNESS_INTERFACE2 interface. • When Windows sets the current scenario by using the DxgkDdiSetBacklightOptimization function, the WDDM driver is required to honor the intent of the scenario as follows: • DxgkBacklightOptimizationDisable: Driver is required to completely disable all backlight optimization. • DxgkBacklightOptimizationDesktop: Driver is required to enable backlight optimization at a lower aggressiveness level.

Driver must optimize for scenarios like photo viewing, browser, and Office documents. • DxgkBacklightOptimizationDynamic: Driver is required to enable backlight optimization at a higher aggressiveness level. Driver must optimize for scenarios like video playback and gaming. • DxgkBacklightOptimizationDimmed: Driver is required to enable backlight optimization at a higher aggressiveness level.

Driver must make sure that the content on the screen is visible but it need not be easily readable. • Driver is allowed to dynamically change the aggressiveness level based on the content on the screen.

• Driver is required to handle Windows requests for change to brightness level (based on user input or ambient light sensor) while keeping backlight optimization enabled. • Driver is required to gradually transition between aggressiveness levels: • This is important in the case when user briefly invokes playback controls. At that time, Windows will reset the scenario from DxgkBacklightOptimizationDynamic to DxgkBacklightOptimizationDesktop. The transition must not be a step but must be gradual. • WDDM driver is required to provide accurate information when Windows queries DxgkDdiGetBacklightReduction. • Connecting additional display devices to the system must not impact the ability to perform backlight optimization on the integrated panel of the system.

System.Client.BrightnessControls.BrightnessControlButtons Systems that have built in physical brightness control function keys use standard ACPI events and support control of LCD backlight brightness via ACPI methods in the system firmware. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Windows Server 2016 x64 Description Windows provides users with an LCD brightness control user interface. If the system implements keys that are invisible to the operating system, these keys must use Advanced Configuration and Power Interface (ACPI) methods. These keys must not directly control the brightness after Bit 2 of the _DOS method has been set. This requires the implementation of ACPI brightness methods in the system firmware.

The following methods are required: • _BCL • _BCM Bit 2 of the _DOS method must be disabled so that the system firmware cannot change the brightness levels automatically. The following methods are optional: Support for the _BQC method is highly recommended but not required. Systems must map keys to the following ACPI notification values: • ACPI_NOTIFY_CYCLE_BRIGHTNESS_HOTKEY 0x85 • ACPI_NOTIFY_INC_BRIGHTNESS_HOTKEY 0x86 • ACPI_NOTIFY_DEC_BRIGHTNESS_HOTKEY 0x87 • ACPI_NOTIFY_ZERO_BRIGHTNESS_HOTKEY 0x88 Design Notes: The _BCL and _BCM methods in the firmware enable the operating system to query the brightness range and values and to set new values. Refer to the ACPI 3.0 specification for more details. System.Client.BrightnessControls.SmoothBrightness Driver must support a smooth transition in response to all brightness change requests from Windows. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Windows Server 2016 x64 Description • All Windows systems that support brightness control, are required to support smooth brightness control • All Windows systems are required to report 101 brightness levels to Windows. Brightness is reported as a% so this means 0 to 100 levels, including 0 and 100.

Internally the driver might support more granular brightness control. • This is to ensure that Windows has the ability to make fine grained changes to the screen brightness. However, the brightness slider UI might expose fewer levels through the slider because it might be cumbersome for the user to adjust so many levels. • WDDM driver is required to implement smooth brightness control in the driver without depending on the embedded controller (EC) for the smoothness.

• WDDM driver is required to indicate support for smooth brightness control using the capability bit defined in the DXGK_BRIGHTNESS_INTERFACE2 interface. • WDDM driver must enable/disable smooth brightness control based on state set using DxgkDdiSetBrightnessState. • When Windows requests a change to brightness, driver is required to gradually change the brightness level over time so that the change is not a step. • WDDM driver is allowed to select an appropriate slope for transition.

However, the transition must complete in less than 2s. • WDDM driver is allowed to alter the slope based on panel characteristics to ensure smoothness of brightness control. • WDDM driver is required to start responding immediately to new brightness level requests. This must be honored even if the system is already in the process of an existing transition. At such a time, the system must stop the existing transition at the current level and start the new transition from the current position. This will ensure that when a user is using the slider to manually adjust the brightness, the brightness control is still responsive and not sluggish.

• WDDM driver is required to continue supporting smooth brightness control, even if content based adaptive brightness optimization is currently in effect. • When WDDM driver is pnp started, it must detect the brightness level applied by the firmware and smoothly transition from that level to the level set by Windows.

• Connecting additional display devices to the system must not impact the ability to do smooth brightness control on the integrated panel of the system. • Brightness levels are represented as a% in Windows. Therefore there is no absolute mapping between brightness% level and physical brightness level. For Windows 8, the following is the guidance.

Percent represented to Windows User Experience 0% Brightness level such that the contents of the screen are barely visible to the user 100% Max brightness supported by panel System.Client.Buttons System.Client.Buttons.HardwareButtons Hardware buttons are implemented correctly Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description This requirement is currently optional and will not be enforced until 2017. Hardware buttons must be implemented according to the guidance on the following page: GPIO buttons must be specified using the standardized ACPI generic button device (ACPI0011): In the case where buttons are not wired through GPIO interrupts, buttons must be reported to Windows as HID collections. HID button report descriptors must follow the report descriptors specified on the following page: System.Client.Camera System.Client.Camera.Device Systems with integrated cameras must meet camera device requirements.

Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description Each integrated camera on a system must comply with Device.Streaming.Camera.Base and all related requirements. If the integrated camera is a USB camera, it must also comply with Device.Streaming.Camera.UVC for the system seeking certification. Note: With regards to ‘ Device.Streaming.Camera.Base.UsageIndicator’ if a system has multiple cameras, then one physical indicator (e.g. LED) is acceptable so long as it indicates usage whenever one or more cameras are in use.

Systems without a display must have a physical indicator. System.Client.Camera.PhysicalLocation Systems with integrated cameras must report the physical location of each camera. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description For any camera device that is built into the chassis of the system and has mechanically fixed direction, the firmware must provide the _PLD method and set the panel field (bits [69:67]) to the appropriate value for the panel on which the camera is mounted. For example, 'Front' indicates the camera faces the user, while 'back' indicates that the camera faces away from the end user. In addition, bit 143:128 (Vertical Offset), and bits 159:144 (Horizontal Offset) must provide the relative location of the camera with respect to the display. This origin is relative to the native pixel addressing in the display component. The origin is the lower left hand corner of the display, where positive Horizontal and Vertical Offset values are to the right and up, respectively.

For more information, see the ACPI version 5.0 Section 6.1.8 'Device Configuration _PLD (Physical Device Location).' Camera device orientation with respect to the default system display orientation (also known as native system display orientation) must be specified in the _PLD rotation field (bits 115-118). When the pixels read out from the camera sensor can be displayed correctly without any rotation, then the camera sensor’s _PLD rotation value must be set to 0. When the pixels read out from the camera sensor need to be rotated clockwise to display correctly, then the camera sensor’s _PLD rotation value must be set accordingly (‘0’ for 0°, ‘2’ for 90°, ‘4’ for 180°, and ‘6’ for 270°). All other fields in the _PLD are optional. System.Client.Camera.VideoCaptureAndCameraControls Systems with integrated cameras meet the requirements of, and can support the Windows Capture Infrastructure. Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Description System Memory: System Memory must be supported.

Independent Streaming: All integrated Cameras must support independent streaming between different pins and different filters (cameras) according to the capabilities listed in the Profiles advertised by the device. If the camera does not support Profiles, then concurrent streaming for all system cameras is optional. Mirroring: The default state for mirroring must be 'not mirrored.' Camera Controls (If Implemented): Each of the following camera controls are optional. • Region of Interest (ROI) • Focus • Exposure • White Balance • Zoom • Camera Flash • Scene Mode • Optimization Hints • Optical Image Stabilization • Backlight Compensation • Brightness • Contrast • Exposure Compensation • Hue • Pan • Tilt • Roll • Video Stabilization • Variable Frame Rate • Face Detection • Video HDR • Histogram • Advanced Photo If any individual control is implemented in the camera driver, it must comply with the control specification in the WDK. Photo Sequence (If Implemented): Photo Sequence captures a sequence of photos in response to a single photo click.

Capture pipeline would send buffers to the camera driver continuously to capture the photos in sequence. This mode also allows capturing photos from the time before the “user click” thus helping users not to lose a moment. If camera HW supports Photo Sequence, it must expose the capability through the Photo Mode property and comply with the performance requirements. Photo Sequence must be enabled by the device and driver to: • Support the same resolutions that are exposed in Normal mode • Report the current frame rates possible in Photo Sequence Mode based on the current light conditions. Device must honor and not exceed the maximum frame rate set by the application. • Support at minimum 4fps measured at lesser of the maximum resolution exposed by the image pin or 8MP.

• Provide at least 4 frames in the past at lesser of the maximum resolution exposed by the image pin or 8MP. • Photo Sequence should be performed independently, regardless preview on/off. • Provide frames continuously in Photo Sequence mode at lesser of the maximum resolution exposed by the image pin or 8MP. • If the driver outputs JPEG format for Photo Sequence it must also support thumbnails, upon request, at 1/2x, 1/4x, 1/8x, and 1/16x of the width and height of the original image resolution. • The JPEG image generated by the camera may optionally have EXIF metadata indicating the “flash fired” information.

EXIF information shall not include personally identifiable information, such as location, unique ids, among others. Variable Photo Sequence (If Implemented): Variable Photo Sequence captures a finite number of images and supports the ability to vary the capture parameters for each of the captured images.

If implemented in Camera driver then the driver should be able to return the requested number of images, in order, each with varying capture parameters as instructed by the application. The driver shall be able to preprogram the number of frames needed and set independent capture parameters for each frame before capture is initiated. It is recommended that the variable photo sequence allows the application to specify the following parameters for each frame, but at least one of these must be implemented if VPS is supported: • Exposure • ISO • Exposure Compensation in EV • Focus position • Flash If any parameter is not set in per frame settings the driver shall follow the global settings and 3A locks. For example when EV bracketing is used, the driver shall ensure that exposure related parameters like gain and exposure are set according to EV bracketing settings.

The driver may vary auto white balance settings for image frames unless the per frame settings use manual white balance settings or in case of application uses white balance lock. It not recommended that lens position is automatically changed between the VPS frames (unless manually specified by the application). System.Client.Digitizer System.Client.Digitizer.Base.SystemDigitizerBase System Digitizer Base Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x86 Windows 10 Mobile ARM Windows 10 Mobile x86 Windows Server 2016 x64 Description The following Digitizer Base device level requirements must be met and verified upon integration into a system. Please refer to the following Device.Input.Digitizer.Base requirements for full requirement details: • Device.Input.Digitizer.Base.ContactReports • Device.Input.Digitizer.Base.HIDCompliant • Device.Input.Digitizer.Base.ThirdPartyDrivers System.Client.Digitizer.SystemPen System Pen Applies to Windows 10 Mobile ARM Windows 10 Mobile x86 Description The following Pen device level requirements must be met and verified upon integration into a system. Warning Certification for Windows Server 2016, Azure Stack, and SDDC must continue to meet the Windows Hardware Compatibility Requirements as stated in version 1607 of documentation, must use with and supplemental content to generate logs, and must follow policies as stated in the. Questions about the Azure Stack or SDDC programs or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact. System.Fundamentals.Security.DGCG.CredentialGuard This feature checks for Credential Guard.

Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows Server 2016 x64 Terms: If-Implemented Description: The following table shows the hardware, firmware and software requirements for Credential Guard. • MUST meet all Device Guard requirements as described in System.Fundamentals.Security.DeviceGuard. (except for the need of HVCI compatible drivers and Firmware UEFI NX Protection) • MUST meet the additional requirements as described in the table below: Requirement Description Trusted Platform Module (TPM) version 1.2 or 2.0 TPM 1.2 and 2.0 provides protection for encryption keys that are stored in the firmware. Either discrete or firmware TPMs will suffice. Secure MOR Revision 2 bit prevents certain memory attacks and is necessary for Credential Guard. This will further enhance security of Credential Guard.

System.Fundamentals.Security.DGCG.DeviceGuard Device Guard requirement for systems Applies to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) x64 Windows Server 2016 x64 Terms: If-Implemented Description Windows 10 has an optional feature called that gives organizations the ability to lock down devices in a way that provides advanced malware protection against new and unknown malware variants as well as Advanced Persistent Threats (APTs). The following table shows the hardware, firmware and software requirements for Device Guard. • MUST meet all Driver requirements as described in “Filter.Driver.DeviceGuard.DriverCompatibility”.

• MUST meet the additional requirements as described in the table below: Requirement Description Windows 10 OS SKUs The PC must be running Windows 10 Enterprise, Windows 10 Education, Windows Server 2016, Windows 10 Mobile Enterprise x64 architecture The features that virtualization-based security uses in the Windows hypervisor can only run on a 64-bit PC. UEFI firmware version 2.3. Traktor Scratch Pro 2 Torrent Windows 7 here. 1 or higher with UEFI Secure Boot and Platform Secure Boot UEFI Secure Boot ensures that the device boots only authorized code. Additionally, Boot Integrity (aka Platform Secure Boot) must be supported following the requirement in Hardware Compatibility Specification for Systems for Windows 10: (this includes Hardware Security Test Interface) Secure firmware update process System Firmware must support field updates through Windows Update. UEFI firmware must support secure firmware update as described in. Firmware BIOS lockdown Required BIOS capabilities: BIOS password or stronger authentication supported to ensure that only authenticated Platform BIOS administrator can change BIOS settings OEM supports capability to add OEM or Enterprise Certificate in Secure Boot DB at manufacturing time. Protected BIOS option to configure list of permitted boot devices and boot device order which overrides BOOTORDER modification made by OS (e.g.

Boot only from internal hard drive). Required Configurations: Microsoft UEFI CA must be removed from Secure Boot DB. Support for 3rd-party UEFI modules is permitted but should leverage ISV-provided certificates or OEM certificate for the specific UEFI software (e.g. How To Break Into A Combination Sentry Safe Lockbox.

Software package “foo” certificate). BIOS options related to security and boot options must be secured to prevent other operating systems from starting and to prevent changes to the BIOS settings.

BIOS authentication must be set (e.g. BIOS password must be set) Virtualization extensions The following virtualization extensions are required to support virtualization-based security: • Intel VT-X or AMD-V • Second Level Address Translation (Intel Extended Page Tables, AMD Rapid Virtualization Indexing) VT-D or AMD‑Vi IOMMU (Input/output memory management unit) In Windows 10, an IOMMU enhances system resiliency against memory attacks.

For more information, see ACPI description tables. () UEFI NX Protections • All UEFI memory that is marked executable must be read only. Memory marked writable must not be executable. • UEFI runtime services must meet these requirements: • Implement the UEFI 2.6 EFI_MEMORY_ATTRIBUTES_TABLE. The entire UEFI runtime must be described by this table. • All entries must include attributes EFI_MEMORY_RO, EFI_MEMORY_XP, or both. • No entries must be left with neither of the above attribute, indicating memory that is both executable and writable.

Memory must be either readable and executable or writeable and non-executable. Firmware support for SMM protection The Revision 1, April 18, 2016 specification contains details of an Advanced Configuration and Power Interface (ACPI) table that was created for use with Windows operating systems that support Windows virtualization-based security (VBS) features. For more information, see the Windows SMM Security Mitigations Table (WMST) specification. () System.Fundamentals.ServerNano Basic requirements for the Nano Server installation option of Windows Server. Warning Certification for Windows Server 2016, Azure Stack, and SDDC must continue to meet the Windows Hardware Compatibility Requirements as stated in version 1607 of documentation, must use with and supplemental content to generate logs, and must follow policies as stated in the. Questions about the Azure Stack or SDDC programs or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact. Warning Certification for Windows Server 2016, Azure Stack, and SDDC must continue to meet the Windows Hardware Compatibility Requirements as stated in version 1607 of documentation, must use with and supplemental content to generate logs, and must follow policies as stated in the.

Questions about the Azure Stack or SDDC programs or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact. Warning Certification for Windows Server 2016, Azure Stack, and SDDC must continue to meet the Windows Hardware Compatibility Requirements as stated in version 1607 of documentation, must use with and supplemental content to generate logs, and must follow policies as stated in the. Questions about the Azure Stack or SDDC programs or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact. Applies to Windows Server 2016 x64 Description Server systems must include the following devices or functionality. Warning Certification for Windows Server 2016, Azure Stack, and SDDC must continue to meet the Windows Hardware Compatibility Requirements as stated in version 1607 of documentation, must use with and supplemental content to generate logs, and must follow policies as stated in the. Questions about the Azure Stack or SDDC programs or how to submit the results for solution validation should be directed to the appropriate Microsoft technical account manager or partner management contact. Applies to Windows Server 2016 x64 Terms: If-Implemented Enforcement Date: October 1, 2017 Description Platforms must meet the following requirements: • The device location must be described as a string, which is provided by _DSM function 7, as described in the PCI Firmware Specification Revision 3.1.

• The device location string must match the text physically printed on the system (e.g. A motherboard silkscreen, an etched drive bay number, or a legend printed on a tray). System.Server.DynamicPartitioning This feature defines dynamic partitioning requirements of server systems. This feature is not required of all server systems. System.Server.DynamicPartitioning.Application Servers that support hardware partitioning must supply partition management software as a Windows application running on a Windows operating system. Applies to Windows Server 2016 x64 Description Servers that support hardware partitioning must provide partition manager software, which provides the user interface administrators will use to configure hardware partitions. This software must be offered as a Windows application running on a Windows operating system.

System.Server.DynamicPartitioning.ApplicationInterface Servers that support hardware partitioning must supply partition management software that provides a GUI and a scripting capability for partition management. Applies to Windows Server 2016 x64 Description Servers that support hardware partitioning must supply partition management software that includes support for a graphical user interface for manual partition management and a scripting capability for remote or automated partition management. System.Server.DynamicPartitioning.ConfigurationPersist Servers that support hardware partitioning must support persistence of hardware partition configuration information across a reboot and power cycle.

Applies to Windows Server 2016 x64 Description The hardware partition configuration on a server that supports hardware partitioning must persist across a reboot, hibernate, resume, and power cycle of the partition or the server. This requirement assumes that no partition change was initiated while the partition was down.

System.Server.DynamicPartitioning.Core Systems that support Dynamic Hardware Partitioning must meet requirements.