(11-27-2023, 10:45 AM)Steve2926 Wrote: Then, if required, you can scan drive using photorec for known files (but it will be very slow and large files may only be partially recovered or corrupt).
All this Ventoy stick is to do easily again. (From archive.)
There is no need at all, to recover anything.
It is about, how to remove this unbootable, this read-only situation.
I now did try lots of tools and software, until very old Low Level Format (DOS Floppy-Disks) from Western Digital, because SanDisk is from them. Nothing helps.
But now bought a new stick. Did create the Ventoy again.
Then - accidentily - I could see with GParted, that - at least; first - one partition is marked as read-only, with a yellow exclamation mark. And depending on what You do further, for tests, also orange or red; always as sign to see for this read-only status.
And this here, without any boot-error - it is to boot, and further ISOs are to add -, despite this read-only ...
What I really do not need now, is many many explanations to that.
But to me now this just says: oh, Ventoy creates ´some kind´ of read-only.
And my - accidentily - using of (diskpart) bcdboot - accidentily using this parameter - ´/all´, did have this effect to the stick, that it is no more bootable, and this read-only no more to remove, on usual ways.
(The bcdboot command I had to use as last command, to repair boot error from a Win10 installaton, which now works again.
But with now knowing this, I would never use this all parameter or/and plug off just the stick, before running this command.
Or: too said, that this stick has no hardware-switch for write-protection ... )
