Legacy download files
To connect the adapter and use an Ethernet connection. Plug the USB-C connector on the adapter into the USB-C port on your Surface device. The driver will install automatically and take a few moments. Take an Ethernet cable that’s plugged into a router, switch, hub, or modem, and then plug the other end into the Ethernet jack on the adapter. Get drivers and downloads for your Dell Surface Pro 4. Download and install the latest drivers, firmware and software.
Legacy PROWIN32 and PROWIN64 download packages provide PROSet, driver, ANS, FCoE, and DCB support for Windows 7* and Windows Server 2008 R2*.
![Driver Driver](/uploads/1/2/5/8/125860152/916529339.jpg)
![Surface Ethernet Adapter Driver Download Surface Ethernet Adapter Driver Download](/uploads/1/2/5/8/125860152/612873131.jpg)
Regular webpacks provide Intel® PROSet support for operating systems Windows 8.1*, Windows Server 2012*, Windows Server 2012 R2*, Windows® 10, Windows Server 2016*, or newer supported operating systems.
Note: New hardware support or new features will not be added to legacy download packages.
Overview
This download contains the Intel® Ethernet network drivers and software for Windows 7*.
Which file should you download?
Note: 10GbE adapters are only supported by 64-bit drivers:
- PROWin32.exe for 32-bit (x86) editions of Windows*
- PROWinx64.exe for 64-bit (x64) editions of Windows
How to use this download
Download the self-extracting archive and run it. It will extract the files to a temporary directory, run the installation wizard, and remove the temporary files when the installation is complete. All language files are embedded in this archive. You do not need to download an extra language pack.
See readme notes if you want to extract the files without installing.
This software may also apply to Intel® Ethernet Controllers. Support for built-in network connections is provided by the system or board manufacturer.
About Intel® drivers
The driver or software for your Intel® component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.
See list of manufacturers’ Support websites.
-->How you manage Surface driver and firmware updates varies depending on your environment and organizational requirements. On Surface devices, firmware is exposed to the operating system as a driver and is visible in Device Manager, enabling device firmware and drivers to be automatically updated using Windows Update or Windows Update for Business. Although this simplified approach may be feasible for startups and small or medium-sized businesses, larger organizations typically need IT admins to distributing updates internally. This may involve comprehensive planning, application compatibility testing, piloting and validating updates, before final approval and distribution across the network.
Note
This article is intended for technical support agents and IT professionals and applies to Surface devices only. If you're looking for help to install Surface updates or firmware on a home device, see Update Surface firmware and Windows 10.
While enterprise-grade software distribution solutions continue to evolve, the business rationale for centrally managing updates remains the same: Maintain the security of Surface devices and keep them updated with the latest operating system and feature improvements. This is essential for maintaining the stability of your production environment and enabling users to stay productive. This article provides an overview of recommended tools and processes for larger organizations to accomplish these goals.
Central update management in commercial environments
Microsoft has streamlined tools for managing devices – including driver and firmware updates -- into a single unified experience called Microsoft Endpoint Manager admin center accessed from devicemanagement.microsoft.com.
Manage updates with Endpoint Configuration Manager and Intune
Endpoint Configuration Manager (formerly System Center Configuration Manager) allows you to synchronize and deploy Surface firmware and driver updates with the Configuration Manager client. Integration with Microsoft Intune lets you see all your managed, co-managed and partner-managed devices in one place. This is the recommended solution for large organizations to manage Surface updates.
For detailed steps, see the following resources:
- Deploy applications with Configuration Manager.
Manage updates with Microsoft Deployment Toolkit
Included in Endpoint Configuration Manager, the Microsoft Deployment Toolkit (MDT) contains optional deployment tools that you may wish to use depending on your environment. MDT includes the Windows Assessment and Deployment Kit (Windows ADK), Windows System Image Manager (Windows SIM), Deployment Image Servicing and Management (DISM), and User State Migration Tool (USMT). You can download the latest version of MDT from the Microsoft Deployment Toolkit download page.
For detailed steps, see the following resources:
WindowsPE and Surface firmware and drivers
System Center Configuration Manager and MDT both use the Windows Preinstallation Environment (WindowsPE) during the deployment process. WindowsPE only supports a limited set of basic drivers such as those for network adapters and storage controllers. Drivers for Windows components that are not part of WindowsPE might produce errors. As a best practice, you can prevent such errors by configuring the deployment process to use only the required drivers during the WindowsPE phase.
Supported devices
Downloadable MSI files are available for Surface devices from Surface Pro 2 and later. Information about MSI files for the newest Surface devices such as Surface Pro 7, Surface Pro X, and Surface Laptop 3 will be available from this page upon release.
Managing firmware with DFCI
With Device Firmware Configuration Interface (DFCI) profiles built into Intune (now available in public preview), Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings including boot options and built-in peripherals, and lays the groundwork for advanced security scenarios in the future. For more information, see:
- Ignite 2019: Announcing remote management of Surface UEFI settings from Intune.
Best practices for update deployment processes
To maintain a stable environment and keep users productive, it’s strongly recommended to maintain parity with the most recent version of Windows 10. For best practice recommendations, see Build deployment rings for Windows 10 updates.
Downloadable Surface update packages
Specific versions of Windows 10 have separate .msi files, each containing all required cumulative driver and firmware updates for Surface devices. Update packages may include some or all of the following components:
- Wi-Fi and LTE
- Video
- Solid state drive
- System aggregator module (SAM)
- Battery
- Keyboard controller
- Embedded controller (EC)
- Management engine (ME)
- Unified extensible firmware interface (UEFI)
Downloading .msi files
- Browse to Download drivers and firmware for Surface on the Microsoft Download Center.
- Select the .msi file name that matches the Surface model and version of Windows. The .msi file name includes the minimum supported Windows build number required to install the drivers and firmware. For example, as shown in the following figure, to update a Surface Book 2 with build 18362 of Windows 10, choose SurfaceBook2_Win10_18362_19.101.13994.msi. For a Surface Book 2 with build 16299 of Windows 10, choose SurfaceBook2_Win10_16299_1803509_3. msi.
Figure 1. Downloading Surface updates
Surface .msi naming convention
Since August 2019, .msi files have used the following naming convention:
- ProductWindows releaseWindows build numberVersion numberRevision of version number (typically zero).
Example
- SurfacePro6_Win10_18362_19.073.44195_0.msi
This file name provides the following information:
- Product: SurfacePro6
- Windows release: Win10
- Build: 18362
- Version: 19.073.44195 – This shows the date and time that the file was created, as follows:
- Year: 19 (2019)
- Month and week: 073 (third week of July)
- Minute of the month: 44195
- Revision of version: 0 (first release of this version)
Legacy Surface .msi naming convention
Legacy .msi files (files built before August 2019) followed the same overall naming formula but used a different method to derive the version number.
Example
- SurfacePro6_Win10_16299_1900307_0.msi
This file name provides the following information:
- Product: SurfacePro6
- Windows release: Win10
- Build: 16299
- Version: 1900307 – This shows the date that the file was created and its position in the release sequence, as follows:
- Year: 19 (2019)
- Number of release: 003 (third release of the year)
- Product version number: 07 (Surface Pro 6 is officially the seventh version of Surface Pro)
- Revision of version: 0 (first release of this version)
Learn more
- Deploy applications with Configuration Manager.
- Ignite 2019: Announcing remote management of Surface UEFI settings from Intune.