Surface Pro 4 Windows 8.1 Drivers and Tools

operating-system · driver · recovery · Windows · Microsoft (OS), XDA Member "ptrkhh" (Custom image), WVBCommunity Member "一个技术宅" (BSOD fix and reuplo

Credits: These drivers come from the image at https://xdaforums.com/t/sp4-windows-8-1-custom-rom-for-surface-pro-4.3318751/ , reuploaded by https://community.wvbtech.com/d/1443 along with the BSOD fix at startup. I have extracted them with Export-WindowsDriver -Online from the custom image. What doesn't work: Top buttons are not mapped correctly (power is volume down, volume up is power and volume down is start) Auto-rotate and automatic on screen keyboard don't work after unplugging the type cover. WORKAROUND: This happens because the Surface doesn't recognize when the keyboard is unplugged, so it first has to know it's disconnected/disabled. To disconnect the keyboard and have these work, turn the surface on its side with the keyboard connected to make it disable the type cover and autorotate with it connected, then disconnect the type cover in this state. These 2 things will then work. This works everytime, even if you've already disconnected the type cover in landscape mode without the software knowing it's been disconnected first. Just reconnect it and do this. Sleep and hibernate should be broken when you do the workaround for newer firmwares, but sleep seems to work on the latest firmware. I don't have any setting to enable hibernation in control panel but hybrid startup works fine. Surface app on Windows 8.1 was never updated for the Surface Pro 4 for obvious reasons, so that won't work, and neither does Windows Hello as it's only a thing Windows 10 and up. For additional quirks and info, visit the original XDA thread These drivers have been tested on the original Surface Pro 3 recovery image, but should work on any 8.1 installation. If you get a bluescreen with the INTERNAL_POWER_ERROR code, you have a newer firmware that is incompatible with the intelpep drivers. You have to disable them accordingly (thanks to the guide above for this method): Delete the Windows\System32\DriverStore\FileRepository\intelpep.inf_amd64_xxxxxxxxx folder. Then, open Regedit, load the Windows\System32\config\SYSTEM hive, locate \SYSTEM\ControlSet001\Services\intelpep, and delete the intelpep item. This can be done from either a PE environment, or a normal Windows install if you're dualbooting. There are 2 ways to install these drivers: - via WinNTSetup (incl. a version with ADK downloaded, that can run on a Windows PE environment, including Setup and Recovery), apply a wim to a partition (or vhd if you'd like) and point it to a folder where you extracted the drivers (should be one with all the driver subfolders). It will automatically apply the 100 drivers and they should work right out of the box. NOTE FOR WHO IS DOING THIS IN A DUALBOOT CONFIGURATION WANTING TO USE ANOTHER WINDOWS INSTALL ON THE DEVICE TO DO THE BSOD FIX INSTEAD OF PE: Keep in mind this will set Windows 8 as the default. Set the default os as a working one in msconfig when WinNTSetup prompts you to restart or have a way to boot a working os through Windows Recovery with a Windows Setup USB or similar to avoid getting stuck in a bsod/blue recovery screen (here windows key to select another OS does not work) loop in case your firmware is incompatible. If your SSD is empty/you want to wipe it i recommend you boot into Windows Setup (can be any version from 8.1 or above, as we are not installing windows with this installer), get to the partition selection screen, delete all partitions if you need to, and create a new partition with default of whatever size you want. This will create necessary partitions allowing you to then launch WinNTSetup and go from there (shift+f10 for cmd). Note this will NOT get you the recovery environment, there are ways to get that manually but as there are many resources available online if you really need it you're on your own. Alternatively you can just use the recovery environment on any setup iso. - manually, "updating" the driver on every unknown/exclamation mark device on device manager and pointing it to the aforementioned folder. you need to disable signature enforcement for this to work. could also be integrated into the wim, but i didn't test personally After this, touch may not work (after a 2nd reboot for the first method) because it gets blocked by Windows at boot for not meeting Logo requirements. To fix this, enable test signing by running bcdedit /set testsigning on in an elevated CMD/powershell You will get an annoying watermark, which you can disable with the included Universal Watermark Disabler software. (source: WinAero) If you want to get the Surface Pro 3 image (shown in pictures above) like i did, get a hold of the .zip of the recovery (won't go over that but it's pretty easy), and extract it. Then, inside sources merge the .swm files into a single wim with this guide: https://answers.microsoft.com/en-us/windows/forum/all/combine-installswm-files-in-to-single-installwim/80e6212f-bd63-44d8-91d3-26fe464e67d5 and once you have a wim you can deploy it like above or your favorite method.