http to https

ThirdPartyNotices

@@ -7,7 +7,7 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo
 Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
 may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
 The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
-Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
+Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.
 
 Privacy information can be found at https://privacy.microsoft.com/en-us/
 

windows-driver-docs-pr/3dprint/3d-partner-onboarding-guide.md

@@ -47,7 +47,7 @@ A plug-and-play 3D printer on Windows 10 is implemented through a pair of driver
 
     - Download and install the [Windows 10 SDK](https://go.microsoft.com/fwlink/p/?LinkID=822845)
 
-    - Download and install the [3D printing SDK](http://go.microsoft.com/fwlink/p/?LinkId=394375)
+    - Download and install the [3D printing SDK](https://go.microsoft.com/fwlink/p/?LinkId=394375)
 
    > [!NOTE]
    > The 3D printing SDK will be installed in C:\\Program Files (x86)\\Microsoft SDKs\\3D Printing.

windows-driver-docs-pr/3dprint/3d-printing-partners.md

@@ -8,4 +8,4 @@ ms.localizationpriority: medium
 
 # 3D hardware partners
 
-Microsoft has teamed up with 3D hardware partners to make end-to-end 3D manufacturing accessible to anyone using Windows 10. For the latest information about partners and devices, see the [Hardware partners](http://go.microsoft.com/fwlink/p/?LinkId=627548) site on the Windows Partner Center.
+Microsoft has teamed up with 3D hardware partners to make end-to-end 3D manufacturing accessible to anyone using Windows 10. For the latest information about partners and devices, see the [Hardware partners](https://go.microsoft.com/fwlink/p/?LinkId=627548) site on the Windows Partner Center.

windows-driver-docs-pr/3dprint/enabling-wsprint-on-a-device.md

@@ -84,7 +84,7 @@ For more information on WSPrint 2.0, see the following resources:
 
 [Implementing Web Services on Devices for Printing](https://go.microsoft.com/fwlink/p/?linkid=867155)
 
-[WSPrint 2.0 specification](http://go.microsoft.com/fwlink/p/?LinkId=534008) 
+[WSPrint 2.0 specification](https://go.microsoft.com/fwlink/p/?LinkId=534008) 
 
 
 

windows-driver-docs-pr/3dprint/index.md

@@ -26,13 +26,13 @@ This section provides information about 3D printer drivers in Windows 10.
 
 For the latest information about 3D printing in Windows 10, see the following resources:
 
--   [3D printing on Windows](http://go.microsoft.com/fwlink/p/?LinkId=627554)
--   [3D hardware partners](http://go.microsoft.com/fwlink/p/?LinkId=627548)
--   [3D Builder resources](http://go.microsoft.com/fwlink/p/?LinkId=627556)
--   [3D Builder user's guide](http://go.microsoft.com/fwlink/p/?LinkId=627557)
--   [Channel 9 3D printing blog](http://go.microsoft.com/fwlink/p/?LinkId=624519)
+-   [3D printing on Windows](https://go.microsoft.com/fwlink/p/?LinkId=627554)
+-   [3D hardware partners](https://go.microsoft.com/fwlink/p/?LinkId=627548)
+-   [3D Builder resources](https://go.microsoft.com/fwlink/p/?LinkId=627556)
+-   [3D Builder user's guide](https://go.microsoft.com/fwlink/p/?LinkId=627557)
+-   [Channel 9 3D printing blog](https://go.microsoft.com/fwlink/p/?LinkId=624519)
 
-Download the [Windows 3D Printing SDK](http://go.microsoft.com/fwlink/p/?LinkId=394375) to start developing drivers for printing to a 3D printer.
+Download the [Windows 3D Printing SDK](https://go.microsoft.com/fwlink/p/?LinkId=394375) to start developing drivers for printing to a 3D printer.
 
 ## In this section
 

windows-driver-docs-pr/3dprint/microsoft-standard-driver-for-3d-printers-.md

@@ -28,12 +28,12 @@ The general process to get a 3D printer working on Windows 10 includes the foll
 
 In the following sections, we will illustrate each of these steps using a concrete example.
 
-For more information, see [Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?LinkId=533944).
+For more information, see [Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?LinkId=533944).
 
 ## Compatible ID
 
 
-To specify to the Windows operating system that we are currently using a 3D printer, we have to use the right compatible ID. The list of Microsoft Compatible ID are available at [Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?LinkId=533944).
+To specify to the Windows operating system that we are currently using a 3D printer, we have to use the right compatible ID. The list of Microsoft Compatible ID are available at [Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?LinkId=533944).
 
 The compatible ID for a 3D printer is shown in the following table:
 
@@ -116,7 +116,7 @@ As stated in the above section, IHVs have access to several base configurations.
 
 
 
-For more information about these parameters, please refer to the *MS3DPrint Standard G-Code Driver.docx* document in the [3D Printing SDK](http://go.microsoft.com/fwlink/p/?LinkId=394375) documentation.
+For more information about these parameters, please refer to the *MS3DPrint Standard G-Code Driver.docx* document in the [3D Printing SDK](https://go.microsoft.com/fwlink/p/?LinkId=394375) documentation.
 
 To specify which base configuration to use and which parameters to override, the developer has to specify it through the Extended Properties OS Feature Descriptor as shown here:
 
@@ -158,7 +158,7 @@ static const uint8_t PROGMEM ms3dprint_properties_descriptor[] = {
 };
 ```
 
-Information regarding the extended properties OS feature descriptor are in the *OS\_Desc\_Ext\_Prop.doc* file. See [Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?LinkId=533944) for more information.
+Information regarding the extended properties OS feature descriptor are in the *OS\_Desc\_Ext\_Prop.doc* file. See [Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?LinkId=533944) for more information.
 
 ## Verifying the print capabilities
 
@@ -194,15 +194,15 @@ The 3D Print driver properties can be obtained by visiting the registry at **HKE
 
 For more information, see the following documents and resources:
 
-[3D Printing in Windows](http://go.microsoft.com/fwlink/p/?LinkId=534206)
+[3D Printing in Windows](https://go.microsoft.com/fwlink/p/?LinkId=534206)
 
-[3D Printing SDK (MSI download)](http://go.microsoft.com/fwlink/p/?LinkId=394375)
+[3D Printing SDK (MSI download)](https://go.microsoft.com/fwlink/p/?LinkId=394375)
 
-[Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?LinkId=533944)
+[Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?LinkId=533944)
 
-[USB 2.0 Specification](http://go.microsoft.com/fwlink/p/?linkid=533945)
+[USB 2.0 Specification](https://go.microsoft.com/fwlink/p/?linkid=533945)
 
-You can also contact the Microsoft 3D Printing team at [Ask 3D Printing Questions](http://go.microsoft.com/fwlink/p/?LinkId=534751) (ask3dprint@microsoft.com).
+You can also contact the Microsoft 3D Printing team at [Ask 3D Printing Questions](https://go.microsoft.com/fwlink/p/?LinkId=534751) (ask3dprint@microsoft.com).
 
 
 

windows-driver-docs-pr/3dprint/print-schema-references.md

@@ -15,19 +15,19 @@ The following list provides references and links to industry standards, specific
 
 Crocker, D. and Overell, P. "Augmented BNF for Syntax Specifications: ABNF." The Internet Society. 1997.
 
-[http://www.ietf.org/rfc/rfc2234.txt](http://go.microsoft.com/fwlink/p/?LinkId=780787)
+[http://www.ietf.org/rfc/rfc2234.txt](https://go.microsoft.com/fwlink/p/?LinkId=780787)
 
 **BNF of Generic URI Syntax**
 
 "BNF of Generic URI Syntax." World Wide Web Consortium.
 
-[https://www.w3.org/Addressing/URL/5\_URI\_BNF.html](http://go.microsoft.com/fwlink/p/?LinkId=780788)
+[https://www.w3.org/Addressing/URL/5\_URI\_BNF.html](https://go.microsoft.com/fwlink/p/?LinkId=780788)
 
 **IEEE 754-1985**
 
 Institute of Electrical and Electronics Engineers, Inc (IEEE). "IEEE Standard for Binary Floating-Point Arithmetic." 1985.
 
-[http://ieeexplore.ieee.org/servlet/opac?punumber=2355](http://go.microsoft.com/fwlink/p/?LinkId=780790)
+[http://ieeexplore.ieee.org/servlet/opac?punumber=2355](https://go.microsoft.com/fwlink/p/?LinkId=780790)
 
 **Print Schema Specification**
 
@@ -39,13 +39,13 @@ Microsoft Corporation. "Print Schema Specification."
 
 Bradner, S. "Key words for use in RFCs to Indicate Requirement Levels." The Internet Society. 1997.
 
-[http://www.rfc-editor.org](http://go.microsoft.com/fwlink/p/?LinkId=780795)
+[http://www.rfc-editor.org](https://go.microsoft.com/fwlink/p/?LinkId=780795)
 
 **sRGB**
 
 Anderson, Mathew Srinivasan Chandrasekar, Ricardo Motta, and Michael Stokes. "A Standard Default Color Space for the Internet - sRGB, Version 1.10." World Wide Web Consortium. 1996.
 
-[http://www.w3.org/Graphics/Color/sRGB](http://go.microsoft.com/fwlink/p/?LinkId=780798)
+[http://www.w3.org/Graphics/Color/sRGB](https://go.microsoft.com/fwlink/p/?LinkId=780798)
 
 **Unicode**
 
@@ -55,23 +55,23 @@ The Unicode Consortium. The Unicode Standard, Version 4.0.0, defined by: The Uni
 
 Bray, Tim, Eve Maler, Jean Paoli, C. M. Sperlberg-McQueen, and François Yergeau (editors). "Extensible Markup Language (XML) 1.0 (Fourth Edition)." World Wide Web Consortium. 2006.
 
-[http://www.w3.org/TR/2006/REC-xml-20060816/](http://go.microsoft.com/fwlink/p/?LinkId=780799)
+[http://www.w3.org/TR/2006/REC-xml-20060816/](https://go.microsoft.com/fwlink/p/?LinkId=780799)
 
 **XML Namespaces**
 
 Bray, Tim, Dave Hollander, Andrew Layman, and Richard Tobin (editors). "Namespaces in XML 1.0 (Second Edition)." World Wide Web Consortium. 2006.
 
-[http://www.w3.org/TR/2006/REC-xml-names-20060816/](http://go.microsoft.com/fwlink/p/?LinkId=780800)
+[http://www.w3.org/TR/2006/REC-xml-names-20060816/](https://go.microsoft.com/fwlink/p/?LinkId=780800)
 
 **XML Schema**
 
 Beech, David, Murray Maloney, Noah Mendelsohn, and Henry S. Thompson (editors). "XML Schema Part 1: Structures," Second Edition. World Wide Web Consortium. 2004.
 
-[http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/](http://go.microsoft.com/fwlink/p/?LinkId=780801)
+[http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/](https://go.microsoft.com/fwlink/p/?LinkId=780801)
 
 Biron, Paul V. and Ashok Malhotra (editors). "XML Schema Part 2: Datatypes," Second Edition. World Wide Web Consortium. 2004.
 
-[http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/](http://go.microsoft.com/fwlink/p/?LinkId=780802)
+[http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/](https://go.microsoft.com/fwlink/p/?LinkId=780802)
 
 
 

windows-driver-docs-pr/battery/installing-a-battery-driver.md

@@ -55,7 +55,7 @@ The [**INF Manufacturer section**](https://msdn.microsoft.com/library/windows/ha
 
 ### <span id="Models"></span><span id="models"></span><span id="MODELS"></span>*Models*
 
-The [**INF *Models* section**](https://msdn.microsoft.com/library/windows/hardware/ff547456) specifies the PnP hardware ID of the battery (shown as *pnpid* in the example). If the device is enumerated through ACPI, this section must also specify the EISA-style ID (shown as *acpidevnum*). For information about creating these IDs, see the *Advanced Configuration and Power Interface Specification*, which is available through the [ACPI / Power Management](http://go.microsoft.com/fwlink/p/?linkid=8760) website.
+The [**INF *Models* section**](https://msdn.microsoft.com/library/windows/hardware/ff547456) specifies the PnP hardware ID of the battery (shown as *pnpid* in the example). If the device is enumerated through ACPI, this section must also specify the EISA-style ID (shown as *acpidevnum*). For information about creating these IDs, see the *Advanced Configuration and Power Interface Specification*, which is available through the [ACPI / Power Management](https://go.microsoft.com/fwlink/p/?linkid=8760) website.
 
 ``` syntax
 [MyCompany]

windows-driver-docs-pr/battery/sample-ups-minidriver.md

@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 ## <span id="ddk_sample_ups_minidriver_kg"></span><span id="DDK_SAMPLE_UPS_MINIDRIVER_KG"></span>
 
 
-A sample UPS minidriver is provided in the \\src\\general\\ups subdirectory of versions of the Windows Driver Development Kit (DDK) prior to Windows Vista. The sample contains code and comments to assist you in developing a UPS minidriver DLL. You can download the Windows Server 2003 SP1 DDK, which contains this sample, from the [DDK archive](http://go.microsoft.com/fwlink/p/?linkid=21859).
+A sample UPS minidriver is provided in the \\src\\general\\ups subdirectory of versions of the Windows Driver Development Kit (DDK) prior to Windows Vista. The sample contains code and comments to assist you in developing a UPS minidriver DLL. You can download the Windows Server 2003 SP1 DDK, which contains this sample, from the [DDK archive](https://go.microsoft.com/fwlink/p/?linkid=21859).
 
 
 

windows-driver-docs-pr/bluetooth/bluetooth-certification.md

@@ -12,14 +12,14 @@ ms.localizationpriority: medium
 ## <span id="Where_are_the_Windows_Hardware_Certification_Program_requirements_for_Bluetooth_wireless_technology_"></span><span id="where_are_the_windows_hardware_certification_program_requirements_for_bluetooth_wireless_technology_"></span><span id="WHERE_ARE_THE_WINDOWS_HARDWARE_CERTIFICATION_PROGRAM_REQUIREMENTS_FOR_BLUETOOTH_WIRELESS_TECHNOLOGY_"></span>Where are the Windows Hardware Certification Program requirements for Bluetooth wireless technology?
 
 
-The Windows Hardware Certification Program specifies the requirements for hardware and software to work optimally with Windows. For specific details about the Windows Hardware Certification Program requirements for Bluetooth radios and devices, see [Windows Hardware Certification Requirements and Policies](http://go.microsoft.com/fwlink/p/?linkid=317937).
+The Windows Hardware Certification Program specifies the requirements for hardware and software to work optimally with Windows. For specific details about the Windows Hardware Certification Program requirements for Bluetooth radios and devices, see [Windows Hardware Certification Requirements and Policies](https://go.microsoft.com/fwlink/p/?linkid=317937).
 
 For general information about the Windows Hardware Certification Program, see the [Windows Hardware Certification Kit (HCK)](https://go.microsoft.com/fwlink/p/?LinkId=733613) documentation.
 
 ## <span id="do_windows_8.1_and_windows_8_have_new_bluetooth_requirements_"></span><span id="DO_WINDOWS_8.1_AND_WINDOWS_8_HAVE_NEW_BLUETOOTH_REQUIREMENTS_"></span>Do Windows 8.1 and Windows 8 have new Bluetooth requirements?
 
 
-For Windows 8.1 and Windows 8, the Windows Hardware Certification Program requires Bluetooth radios to support Bluetooth version 4.0 to qualify for a Windows logo. Updated tests are included in the latest version of the HCK. For more information about where to download the HCK, see [Windows Hardware Certification Requirements and Policies](http://go.microsoft.com/fwlink/p/?linkid=317937).
+For Windows 8.1 and Windows 8, the Windows Hardware Certification Program requires Bluetooth radios to support Bluetooth version 4.0 to qualify for a Windows logo. Updated tests are included in the latest version of the HCK. For more information about where to download the HCK, see [Windows Hardware Certification Requirements and Policies](https://go.microsoft.com/fwlink/p/?linkid=317937).
 
 
 

windows-driver-docs-pr/bluetooth/bluetooth-driver-stack.md

@@ -20,7 +20,7 @@ The following image shows the modules within the Bluetooth driver stack, along w
 ![diagram illustrating the bluetooth driver stack](images/bluetooth-architecture.png)
 
 -   **User-mode**
-    -   **User-mode application**- A user-mode application that accesses the Bluetooth driver stack through published APIs. For more information, see [About Bluetooth](http://go.microsoft.com/fwlink/p/?linkid=50712) in the Windows SDK documentation.
+    -   **User-mode application**- A user-mode application that accesses the Bluetooth driver stack through published APIs. For more information, see [About Bluetooth](https://go.microsoft.com/fwlink/p/?linkid=50712) in the Windows SDK documentation.
 
         **Note**  User-mode applications should link against *BthProps.lib*, instead of *IrProps.lib*, in order to use APIs, such as [**BluetoothSetLocalServiceInfo**](https://msdn.microsoft.com/library/windows/hardware/ff536580).
 

windows-driver-docs-pr/bluetooth/bluetooth-host-radio-support.md

@@ -32,7 +32,7 @@ With Windows, a Bluetooth radio can be packaged as an external dongle or embedde
 A new Bluetooth radio might not match any of the device IDs in the Bluetooth INF (Bth.inf) that is included with Windows. This prevents Windows from loading a Bluetooth stack for the device. IHVs should ensure that their radio works with the native Bluetooth stack in one of the following ways:
 
 - Create an INF for the radio that references Bth.inf. For an example of a vendor-specific INF file for a Bluetooth radio, see [Appendix B: An Example of a Vendor-Provided INF File for Use in Windows Vista](bluetooth-faq--appendix-b.md).
-- Store an extended compat ID OS descriptor in the device firmware that specifies an appropriate compatible and subcompatible ID. For information about extended compat ID OS descriptors, see [Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?linkid=308932).
+- Store an extended compat ID OS descriptor in the device firmware that specifies an appropriate compatible and subcompatible ID. For information about extended compat ID OS descriptors, see [Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?linkid=308932).
 - Force the Bluetooth stack to load
 
 The following procedure summarizes how to use Device Manager to force the Bluetooth stack to load for a new radio:
@@ -47,7 +47,7 @@ For a detailed description of this procedure, see [Appendix A: How to Install an
 
 IHVs should take the following steps to ensure that their Bluetooth radios have in box support on Windows:
 
-- Ensure that the radio supports the extended compat ID OS feature descriptor. For details, see [Microsoft OS Descriptors](http://go.microsoft.com/fwlink/p/?linkid=617154).
+- Ensure that the radio supports the extended compat ID OS feature descriptor. For details, see [Microsoft OS Descriptors](https://go.microsoft.com/fwlink/p/?linkid=617154).
 - Obtain Windows Certification Program approval for the Bluetooth radio hardware and the associated INF file. For an example of a vendor-specific INF file for a Bluetooth radio, see [Appendix B: An Example of a Vendor-Provided INF File for Use in Windows Vista](bluetooth-faq--appendix-b.md).
 - Use the Partner Center to make the INF file available through Windows Update
 
@@ -241,7 +241,7 @@ If IHVs do not want Windows to automatically generate a PDO for their device, th
 
 ## How Group Policy can block Bluetooth radio installation
 
-For details on how to use Group Policy to block the installation of Bluetooth radios, see the “Prevent installation of prohibited devices” section of [Step-by-Step Guide to Controlling Device Installation and Usage with Group Policy](http://go.microsoft.com/fwlink/p/?linkid=324335).
+For details on how to use Group Policy to block the installation of Bluetooth radios, see the “Prevent installation of prohibited devices” section of [Step-by-Step Guide to Controlling Device Installation and Usage with Group Policy](https://go.microsoft.com/fwlink/p/?linkid=324335).
 
 Use the following compatible IDs for the Bluetooth radio: