64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
With Windows 10’s Anniversary Update, Microsoft tightened the screws even further. But you can avoid the more restrictive driver-signing requirements by disabling Secure Boot.
Driver Signature Enforcement Is a Security Feature
RELATED:What’s New in Windows 10’s Anniversary Update
Buy it on Amazon.com: Buy it on Amazon.de: Hardware ID: USB VID0CF3&PID9271&REV0108 USB VID0CF3&PID9271 Li.
Before you begin, keep in mind: Microsoft isn’t just trying to make your life harder here. Driver signing enforcement ensures that only drivers that have been sent to Microsoft for signing will load into the Windows kernel. This prevents malware from burrowing its way into the Windows kernel.
![Windows Windows](/uploads/1/2/4/9/124927729/269194858.jpg)
Disable driver signing and you’ll be able to install drivers that weren’t officially signed. Be sure you know what you’re doing! You should only install drivers you trust.
Option One: Enable Test Signing Mode
Windows includes a “Test Mode” or “Test Signing” Mode feature. Enable this mode and driver signature enforcement will be disabled until you choose to leave Test Mode. You’ll see a “Test Mode” watermark appear at the bottom right corner of your desktop near your clock, informing you that Test Mode is enabled.
You’ll need to run a command from an Administrator Command Prompt to do this. To launch one, right-click the Start button or press Windows+X and select “Command Prompt (Admin)”.
Paste the following command into the Command Prompt window and press Enter:
RELATED:How Secure Boot Works on Windows 8 and 10, and What It Means for Linux
If you see a message saying the value is “protected by Secure Boot policy”, that means Secure Boot is enabled in your computer’s UEFI firmware. You’ll need to disable Secure Boot in your computer’s UEFI firmware (also known as its BIOS) to enable test signing mode.
Restart your computer to enter test mode. You’ll see the “Test Mode” watermark appear at the bottom right corner of your desktop and you’ll be free to install whatever unsigned drivers you want.
To leave test mode, open a Command Prompt window as Administrator once again and run the following command:
Option Two: Use an Advanced Boot Option
RELATED:Three Ways to Access the Windows 8 or 10 Boot Options Menu
There’s also another way to do this. You can use the advanced boot options menu to boot Windows 10 with driver signature enforcement disabled. This isn’t a permanent configuration change. The next time you restart Windows, it will boot with driver signature enforcement enabled—unless you go through this menu again.
To do this, get to the Windows 8 or 10 advanced boot options menu. For example, you can hold down the Shift key while you click the “Restart” option in Windows. Your computer will restart into the menu.
Select the “Troubleshoot” tile on the Choose an option screen that appears.
Select “Advanced options”.
Click the “Startup Settings” tile.
Click the “Restart” button to restart your PC into the Startup Settings screen.
Type “7” or “F7” at the Startup Settings screen to activate the “Disable driver signature enforcement” option.
Your PC will boot with driver signature enforcement disabled and you’ll be able to install unsigned drivers. However, the next time you restart your computer, driver signature enforcement will be disabled—unless you go through this menu again. You’re now free to install drivers that haven’t been officially signed by Microsoft.
READ NEXT- › Do You Really Need Antivirus For Your Smart TV?
- › How to Fix a Black Screen After Updating Windows 10
- › How to Use the Linux cat and tac Commands
- › How to See Which Apps Are Using Your Webcam on Windows 10
- › Future Tech: What We’re Most Excited About
See 'WikiDevi' @ the Internet Archive (MW XML, Files, Images)
upgraded MW to 1.30 - maybe things are slightly less broken
upgraded MW to 1.30 - maybe things are slightly less broken
FCC approval date: 04 February 2013
Country of manuf.: China
Country of manuf.: China
ID: 168c:002d (2 addl. devices)
Windows: PCIVEN_168C&DEV_002D
Windows: PCIVEN_168C&DEV_002D
FCC ID:TE7WN751NX
Industry Canada ID: 8853A-WN751NX
Industry Canada ID: 8853A-WN751NX
Probable Linux driver
ath9k (in backports)
PCI ID first seen in kernel v2.6.32 (2009-12-03)
(see also passys)
ath9k (in backports)
PCI ID first seen in kernel v2.6.32 (2009-12-03)
(see also passys)
Antenna connector:RP-SMA
Chip1 brand | Chip2 brand |
---|---|
TP-LINK TL-WN751ND v1 | Atheros |
TP-LINK TL-WN751ND v2 | Atheros |
150Mbps Wireless N PCI Adapter
Product page
Support page
Product page
Support page
- 1x1 SISO
- Single Band
The drivers provided by TP-LINK indicate that this device uses the same chipset (and likely the same PCI ID).
- The chip is clearly visible as AR9227-BC2A in the FCC photos.
'1206042751-2.0' and 'Rev:1.0sp1' is silkscreened on the board in the images provided by TP-LINK and in the FCC photos.
Images[edit]
- from TP-LINK
- angled front
- angled front 2
Retrieved from 'https://wikidevi.com/w/index.php?title=TP-LINK_TL-WN751ND_v2&oldid=112832'