Turns out that Imager seems to have only applied customizations for raspberry pi connect, and nothing else. I connected my pi to a display and had to go through the full first-boot setup from scratch - even though I had already done so in Imager.
Is this:
Is this:
- Imager's fault for not applying customizations, causing the rpi-first-boot wizard to obstruct rpi-connect desktop usage?
- My fault for not updating Imager to 2.0.6?
- Rpi-connect's fault for not working in the first-boot environment?
Statistics: Posted by Botspot — Tue Feb 03, 2026 1:08 am