IS the "windows installation media" portable, or not ?

[qmatch]

Hi !
I've made a bootable win-install SDcard ( a lot, in real ) with an RPi5. Just after that, I've made
an image of that "installer card" too ( I've done this under Windows, with R-Driveimage).
Every "copy" made by this image can work on the same RPi5 device only, where the "original"
installation-card is made. Any other RPi5 can not find "any bootable" just after the UEFI starts.
Is this a feature or a bug ?...or how can I fix this ?

[Marcinoo97]

nothing should be unique to the device you once booted it on. This sounds completely random to me. idk how to fix it. but just for a random test can you replace RPI_EFI.fd on a boot partition with a one from that was never booted from from an uefi zip file (https://github.com/worproject/rpi5-uefi/releases/download/v0.3/RPi5_UEFI_Release_v0.3.zip) before making copy/image?

[qmatch]

An important detail is: I have the newest rpi5, that version "D", what needs the "newest" uefi version. So, basically I have to replace those files made by the wor-flasher, with those ones what made for the new rpi5 - that uefi version called "UEFI5_D0" or smth similar...
I don't see clear the way how the wor-project works, I want to use it "only" - coul'd you tell me something about your idea, better say, something about that RPI_EFI.fd file and its function, please ?

[Marcinoo97]

RPI_EFI.fd is a file that UEFI gets booted from and it stores its settings inside it too. I'm just trying to remember if it stores anything related to serial number or sdcard controller info that could be different between different pi boards. and yes usage of newer UEFI file is better but i didn't know that u did it so.

[qmatch]

...btw I've meant this:
https://github.com/NumberOneGit/rpi5-uefi/tags

[Marcinoo97]

yes, I know. use it.

[qmatch]

Hi again !....
... just today, I've tried it again ( making the install SD , changing UEFI files, then making SD image, then write another SD with this image, then start it in ANOTHER Rpi5 ...blahblah.... ) and it worked well.
I don't understand .... betters say, I replace those UEFI files ( usually ) on a random windows machine with win.FileManager.
What do You think: over the proper content ( I mean the UEFI files ), is the attributes of those replaced files important, or not ?
I can imagine, that we can know less than we should about attributes when moving files, maybe, it is not critical in the
most cases.
So, finally, You are right: there is not any HW-relevant content , what can block the boot/install-procedure... it was something else
in my case.
((( just one more strange piece: there are cases, when I have to cold-start twice the RPi5 with the wininstall-SD, because at the first round NOTHING happens - =black screen only - but after the second try everything is OK !..... so, those lovely secrets.... )))

[qmatch]

Thanks for Your attention...!