We are unifying the driver releases for 12th and 13th gen Intel laptops. Feel free to update your 12th gen system with the new combined installer below.
Driver Bundle
This driver bundle includes several security fixes and enhancements.
The error message 2disbetter reported above comes from the “install_drivers.bat” script in the installer. It checks for strings “FRANMACP” or “FRANMCCP” in %TEMP%\framework_system_report.txt. My framework_system_report has no FRANM* strings.
My 12th gen framework_+system_report.txt does contain:
While I have not tried the new driver installer, I was affected by the initial 3.08 BIOS Updater for Windows refusing my board and it is FRANGACP06 as well. Seems like Framework likes to forget that model exists and has not learned from the last time they forgot it…
Thank you all for these reports. I’m escalating this issue internally so we can take a deeper look into it.
Please let us know if you encounter any other issues or if you have additional screenshots/error messages that can help us identify and solve this problem. Thanks for your cooperation!
I modified the install_drivers.bat to allow 12th Gen product code “FRANGACP” and ran the installer. Everything installed as expected & the system is operating normally.
Note: you can access any of the files in the installer by using a zip utility to unzip the Framework_Laptop_13_12th_and_13th_Gen_Intel_Core_driver_bundle_W11__2024_06_25.exe and reviewing the install_drivers.bat batch file at the top level of the archive.
The change was simple; I’m sure most of you could do it yourselves. But to document one working solution, here’s the change:
Existing install_drivers.bat from Framework:
find “FRANMACP” “%TEMP%\framework_system_report.txt” >nul || (
find “FRANMCCP” “%TEMP%\framework_system_report.txt” >nul || (
echo “This Framework driver bundle is designed to run on 12th&13th Gen Intel Core Mainboards only!”
pause
exit
)
)
Here’s that same section of code updated to allow “FRANGACP” 12th Gen main boards:
find “FRANGACP” “%TEMP%\framework_system_report.txt” >nul || (
find “FRANMACP” “%TEMP%\framework_system_report.txt” >nul || (
find “FRANMCCP” “%TEMP%\framework_system_report.txt” >nul || (
echo “This Framework driver bundle is designed to run on 12th&13th Gen Intel Core Mainboards only!”
pause
exit
)
)
)
Save the updated version to a new name & execute that if the installer failed for your early 12th Gen board.
How about a driver bundle that does not overwrite newer drivers already installed? Many of us update our intel graphics, wifi and BT drivers ourselves. Your bundle does not include the latest drivers in some cases.
The driver bundle includes the latest Framework-certified drivers which may be slightly behind a component manufacturer’s releases. You can always extract specific drivers from the bundle should you wish to only update specific things. Having the driver bundle overwrite existing drivers is advantageous for people who wish to revert the Framework’s recommend configuration.
PS: for all those that did not want to use the bundle because of downgrading risks, fascinatingly, the Intel WiFi and BT drivers at least seem to have it built in to not downgrade. So the most important ones for security, that Windows itself has updated to way newer versions are not a problem…
Would be sensible if Framework could state which drivers handle it this way and will only be applied if they are newer then the ones already installed. Even if this discussion came up more for the other CPU models.
