@linuxssd Windows to Go with Rufus should work. We do not have a Linux-compatible update tool.
@linuxssd Windows to Go with Rufus should work. We do not have a Linux-compatible update tool.
@The Sabrent Informer I have tried with the drive both in a m.2 slot and in an USB4 ASM2464PD enclosure that uses PCIe tunneling which should function just like a m.2 slot. I've done all sorts of firmware operations through the ASM2464PD with a ton of different NVMe drives and it's behaved just like a m.2 slot and I never had any problems with it. But anyways, I don't think having any sabrent drive connected matters when first unpacking the exe file, which is when I get the missing pcie_dll.dll error. When I got the error, I tried it on other systems to see if same thing would happen and it does. My main test system is an Intel NUC 11 Performance, but I also tried it on a various other NUCs (Raptor Lake) and laptops (Alder Lake and Lunar Lake) that I had after that. It just doesn't get past the first extraction stage. I'm sure the program might care about how the drive is connected once it actually runs, but I haven't really gotten to that point yet.
The R184PL.x variant is still a Phison E18 controller with 2gb of DRAM cache correct? I will probably have to peel the paper sticker on the back of the drive to peek at the NAND chip markings in order to find out if it is BiCS (do you know if it would be 5, 6, or 8?), Micron B58R, or something else. Is there a later firmware than R184PL.2? I'm hoping maybe there is a firmware that helps with the disconnections with an enclosure. The disconnects only happen with extended heavy writes. I thought initially it was heat related, but the enclosure I'm using has an outstanding thermal solution and I verified by monitoring temps during the writes and the drive is staying very cool.
