Framework Laptop 13 (Intel® Core™ Ultra Series 1) Driver Bundle v1.03 2025_10_28 Release STABLE

Driver Bundle

Windows 24H2/25H2

Download Link SHA256
Framework_Laptop_13_Intel_Core_Ultra_Series1_driver_bundle_W11_v1.03_2025_10_28.exe 9A8B9A6957898C06189842CFC5055B453F3B32007B17E32AB72E587D9A474BC4

Driver Bundle Components

Driver Version Updated
Intel Chipset 10.1.20256.8665 Updated
Intel GNA 03.05.00.1578 Same
Intel Management Engine 2512.7.3.0 Same
Intel Management and Security Status 2512.7.3.0 Same
Intel Serial IO 30.100.2418.12 Same
Intel Display 31.0.101.7026 Updated
Intel NPU 32.0.100.4023 Same
Intel Dynamic Tuning 9.0.11909.60720 Same
Intel Smart Sound 20.40.12061.0 Same
Realtek Audio 6.0.9859.1 Same
Intel PROSet WiFi 23.160.1.2 Updated
Intel PROSet Bluetooth 23.160.0.9 Updated
Intel Platform Monitoring Technology 3.1.2.6 Same
Goodix Fingerprint 3.12804.1.270 Same
Framework EC 0.0.0.6 Same
Realtek Ethernet 11013_20_07272023_08042023 Same
SD Card Reader v4_5_10_201 Same
2nd Gen uSD Card Reader v4_5_10_202 Same
1 Like

I cannot install these drivers! Attempting to install a download Windows 11 Pro on a FW 13 Intel Ultra 7 155H used Windows Installer on a USB. The program runs but HANGS when it gets to the driver. It cannot access the internet without a driver and the drivers that come with Windows installer won’t work and of course it can’t get to FW site to download them. I downloaded the drives and BIOS for the Ultra series from FW. BUT FW did not give the the option of what LOCATION to download them to so I could not download them directly to the windows installation USB drive, the ONLY thing FW would do was to download them to the downloads folder on the (DIFFERENT) computer I was downloading them with (this is an installation to a NEW PCIe drive). My computer currently does not have ANY windows, so did it on a different computer. When I tried to copy the drivers from the Downloads folder to the USB drive I got the message “(driver bundle) has properties that can’t be copied to the new location”. {as usual with MS, no details are given}
I tried the installation hoping that maybe the lost properties wouldn’t cause a problem but it didn’t work.

The windows installer drivers won’t allow my FW13 to connect to the internet (connection is well established and works on the FW13 when it’s running Ubuntu (on a different PCIe) to get FW’s drivers. I can’t download the drivers to the windows installer USB drive without corrupting them. I can’t download the drivers directly to the PCIe I’m attempting to install them on even if I put it into an enclosure and connect it to a different computer to do the download because FW download DOES NOT GIVE THE OPTION TO SELECT LOCATION.

How do I get around this?

The program runs but HANGS when it gets to the driver. What do you mean? Do you mean you saw the CMD with the cursor but no executing the next steps?

One the first attempt, I planned to download the drivers before porting Windows (11 Pro) which was on the old mainboard (Intel i7 1280P) that died. I hadn’t realized that Windows would attempt to port automatically on startup. It went thru the process to the point where it needed the FW drivers to connect to the net and stopped. I then downloaded the drivers from FW added them to the PCIe drive (and a USB (Ventoy) just in case). Tried again. Stopped at point when it needed to connect to the net. Could not detect the drivers. Trying the Ventoy disk would not work. Dozens of attempts (went thru 2 support tickets with Framework during this weeks long process (with about a 6 week break in the middle just to get away from it for awhile. I tried going on the internet to see what others had done. This was a very common problem at the time. It turned out that the CORE problem was Microsoft’s attempts to BLOCK users from being able to install Windows locally to avoid having their files automatically transferred to MS’s cloud. There were cycles: users would find a hack to get around it and after a couple of weeks MS would do something to block the latest hack. Dozens of such rounds. All involved something MS did to prevent users installing Windows from completing an installation without connecting to the net (at which point MS would set all files to be stored in it’s “cloud”). I got caught up in this when I failed to load the drivers on the target drive before the porting took place. MS treated the lack of drivers as if it was an attempt to install windows locally (which I wasn’t trying to do FWIW) I even tried erasing the PCIe and the USB drive, reinstalling everything again and starting with what I assumed would be a clean slate. Same problems. Tried reformatting everything, reinstalling and again the same result. Even various changes in the BIOS (that were alleged to help) didn’t. A different PCIe didn’t help.

Ubuntu 24.04.4 installed without any problem on the same PCIe with no problems and has worked fine since. I suspect that rules out any problem with the mainboard itself. Since using a different PCIe didn’t help, all I can figure is that MS found a way to make some notation is some memory on the Mainboard (Intel Ultra 1 H155) that tells it that an attempt was made to install windows locally on it and it then refuses to install Windows AT ALL, whether connected to the net or not. Apparently MS got tired of having to find yet another way to block attempts to install locally every few weeks. I WASN"T EVEN TRYING TO! I just didn’t know that Windows would port automatically on startup and I had to install FW drivers BEFOREHAND.

This has been going on for about a year now. I’d given up on windows but there are programs I have that will only work on Windows. So now I want to try again - hoping that by now someone has recognized the problem for what it is and found a way to FIX it.

FWIW I had a fully legal copy of Windows 11 Pro on the old mainboard that died. Eventually having tried everything else imaginable I bought another code for Win 11 Pro and went thru the entire gamut of various “fixes” with it and NOTHING worked. Every single time the code was accepted so that wasn’t the problem.

Also FWIW I have used computers, Windows, Macintosh and Linux, for 4 decades now, always doing my own repairs and upgrades - changing motherboards, WiFi cards, keyboards, displays and everything imaginable (that did not involve soldering) with no problems whatsoever. Which is why THIS one has been so exceptionally aggravating.

I want to try again in case some solution has been found by now.