All the Windows installer will tell me is âThe installer can only be run on Framework Laptop 12 Gen Intel Core Mainboardsâ.
I have a Batch 1 1260p board, running the 3.06 Beta. Are you filtering sth. wrong out? Or is your detection stumbling across some Windows isolation feature?
Can you share your âsystem informationâ summary page?
Kieran
Sure. You mean the MSInfo screen?
(Edit: changed image to one with wider columns so it does not cut off the lines)
@Kieran_Levin Fyi, running the updates manually works (unpacking the msi, executing ME update from within Windows, installing .inf firmware updates and rebooting.) All versions seem on what they are supposed to be
Updated through the EFI shell, everything went fine.
Thanks for the update.
Thank you! I just updated from Windows and so far everything looks good. It did take a bit longer to apply the update than I was expecting, but no errors encountered.
Updated on Linux Fedora 39. No problems once I enabled boot from USB in the BIOS 
The update failed at the first attempt. There was a redirection error in the middle of the update. The usb c ports were not functioning, so the update refused to continue. Had to remove the ssd to make the ports work again, then the update continued.
Had the same issue with the 3.06 update. Yes the drive was definitely cleanly unmounted before attempting the upgrade. These laptops are definitely not the easiest.
Thank you for the release! Itâs also great to see contributions from Dustin Howett, outside of the company Framework!
Knowing what model drive you are using might be a helpful piece of information.
Currently ADATA SX8200PNP 1TB, during 3.06 upgrade last time it had a Kingston FURY Renegade 1TB.
Thank you!
Looks like the update did work here, i7-1280p.
At least, at some point the laptop bootet to Windows again.
I didnât see anything because the lid was closed and there was nothing displayed on the external monitors.
So canât report more than: It works.
Updated from stock 3.04(?) BIOS. Got a gnarly surprise. I was using a rear port to charge the system, and somewhere after about 4 items being flashed it gave me a message about not being able to redirect a file and a script error on line 116.
The system would not charge from the rear left port at that point, and trying to boot the flash drive again left me with a âCONNECT YOUR CHARGERâ message. I moved the USB-C adapter up front and charged from there. After booting off of my USB drive again and maybe 3 or 4 reboots, the system finally completed the process, 5 out of 5 steps. I shut the system down, moved the ports back where I had them, and then booted normally. The operating system (Fedora) reported that the laptop was charging again from the back left port, and at this point everything seems to be normal-ish.
So, if you get a weird message like that, donât panic. Move your ports up front and try again.
Thank you for the update and the clear instructions! Just successfully ran the EFI shell update (Fedora 39 user updating from 3.06 bios) with no immediate issues.
I just tried plugging and unplugging a USB-A thumb drive several times both mounted and unmounted and it was recognized every time! This used to reliably cause an issue that I would remedy by removing and reinstalling the USB-A expansion module.
HDMI and DisplayPort behavior is still weird but appears to be improved. I have earlier versions of both cards and theyâre both behaving better according to powertop. It still seems to change depending on which side I plug them in, seeming to prefer the side opposite the power button, but overall draw seems lower at first glance even with the older cards.
Thanks for this! I was still on 3.04 as well and I was getting the same error but on line 97 during my installation and Iâm still trying to get it to work. Did you have any issues with none of your ports accepting power? Iâm going to keep trying swapping ports around but I think something got screwed up during one of my attempts.
EDIT:
Unplugging the SSD as @Username009 suggested seemed to fix the issue along with moving the power adapter around. I have a Crucial CT500P2SSD8 SSD.
I had the same issue. Whatever the first firmware that was pushed did, it appeared to cause my ports to stop working. I powered off, removed my ports, waited about 30 sec, reinstalled my ports and tried again. The update resumed at the second firmware and completed without issue.
I also had the same issue, that the update failed. I think it was on line 116. I had the stock 3.05 installed.
My device is an i5-1240P with 32 GB 3200 MHz ram and a Samsung SSD 980 PRO 1TB.
The hint from @Username009 to remove the ssd worked, I think. But I also removed the ram, battery, cmos battery and ram, to restore the ability to charge the laptop again. Normal usage of the ports, like the USB and headphone jack extension cards were not affected by the broken update. The possible reason why this âfixedâ this issue can be seen on my second edit of this post.
Although this is a beta release things like this should not happen and a ânormalâ user might think that this bricked their laptop.
EDIT:
Before the update I reset the UEFI to the default configuration. This is something I always do before UEFI updates.
EDIT 2:
It looks like the reason for the âCONNECT YOUR CHARGERâ warning after the failed update was that the laptop is charged to 100%. The laptop disables charging if the laptops battery is fully charged. So it cannot detect if there is a charger connected and thereby this warning gets displayed. By turning it off and removing the battery etc. It dropped to below 100% and enabled the charging again. I think @Kieran_Levin should add a notice to the thread that the laptop should not be fully charged if you try to update the UEFI. I think it should be started with a charging state of around 90% to prevent this issue from happening.
Had the same problem. I just unplugged my external displays.
Thanks for the MSInfo screen, this narrowed down the issue.
Can you try updating with the following and see if it fixes your issue?
Framework_Laptop_12th_Gen_Intel_Core_BIOS__3.08b.msi
Yes, this one runs as expected.
Soo, bug or unusual settings on my machine?
Edit: Btw, because I unpacked the MSI and installed the parts manually, Windows recognized that the BIOS and ReTimer firmwares were up-to-date so did nothing with those, but the ME update that runs directly during the installer executed a 2nd time including the actual flashing.
So seems behavior is not entirely consistent, because it neither does nothing if already updated, but it also does not reinstall all parts in case somebody wanted to do that for some reason.
Edit2: yes the installer seems to explicitly call the ME-Updater with the argument to force updates even if the same version is already installed.
If you get the âCONNECT YOUR CHARGERâ message, I think all you need to do is power down the laptop, unplug it, and wait for a few minutes.
I suggest leaving it unplugged and powered off for a while before you try something more drastic like taking it apart.
