Is there something wrong with upgrading 26200 to 26220? I tried on 2 systems (one VM and one real) and setup never started.
Please read my edit in that post For testing channels i always install the ISO of the build to test and rather not switch (dev and beta).
Me too But that has something to do with the installed cu, being retail channel (iirc), that's why all my different test VMs are installed from the same channel ISO, only a few are clones to test these switches on. Seems with 24/25H2 MSFT is making us re-invent all we knew already
It's should be only affect autostartup programs only, before apply these registry key on 26100.5074, I need to waste about 1-2 minutes to loaded all of autostartup programs for no reason
Also, lesser native flash write speed (aka write speed after cache is filled) which can drop to hdd/usb level 2 digits speeds. 970 Pro was the last samsung retail/consumer ssd to use MLC.
I just bought Samsung only, after the vertex3 drama, and what my budget allowes, now i don't smoke anymore i have a better budget for my main hobby I made 3 exceptions, 2 Adata SU 900 SATAs for older laptops (or wherever i need them in) and now the Lexar M2 (when i had seen that the 990 Pro was in promotion i would have send the Lexar back and got the 990 Pro), but a few weeks later i got me the 990 Pro anyway, the 990 EVO is PCIE 5 but just 2 lanes, so actually it is a PCIE 4 speed drive when it comes to speeds.
Greetings from Peru!!! I hope this helps.... I was testing in a VM the upgrade from 26200.5074 to 26220.5077 using an ISO created from UUPDUMP but the setup file would not even run. After several attempts with the same result, I tested first installing the EP KB5066383 and then trying the 26220.5077 ISO and this time it worked and now my test VM is on 26220.5077. Hope this helps.... JCC2
This works. I'm trying something similar now on a different system by adding KB5066383, KB5065382, KB5043080 and KB5064089 to 26200.5761 and then upgrading.