I didn't create them Can you imagine how i feel after uploading all 304 ISOs with the host just accepting a few Mbit/s upload?
Thank you for your work and especially about uploading to anon services, that website is the best. I use your ISOs all the time! Very useful that you put so much work into this.
Thank you Enthousiast for your answer! Yes, I do have a full backup of my C: drive, but I dunno how or why, the bootloader is not valid anymore, ie I cannot boot from this partition normally, only in safe mode. I suspect Paragon to have installed a win10 bootloader instead of a actual one. But it's not my main problem. I tested the April consumer isos just above, but Rufus still says that their bootloader is revoked. I will now try the MVS versions, and will report if it works. I understand that this situation is entirely my fault, being more than upset by win11 (I have bugs I can't solve, despite having searched anywhere).
Rufus is not anything official, it's not the reference. ALL MSFT ISOs are triggering that message because MSFT still is not complying to that new signing method. Probably the bootloader problems are caused by the bios settings you changed? I hope i can assume the USB drive, containing the backup, was not connected during the installation attempts. About that backup, i meant to have a FULL system backup to be able to restore all partitions and not only the c partition, and if there are other drives, best to disconnect them during clean install (i always do).
Thank you again! I don't have any problems with my other drives, only with the boot (internal nvme SSD) drive. I can obviously disconnect them, being all external drives, but it doesn't change anything. Could you possibly recommend a better Rufus replacement? Considering that my laptop is 100% compatible with win11, I don't need it special functions...
ALWAYS disconnect external drives during windows install and best to disconnect internal drives too, at re-installing windows. You can safely ignore that rufus message about the efi loader stuff.
Ventoy is good, provided a link to the latest version: https://forums.mydigitallife.net/th...iso-files-uefi-too.81633/page-18#post-1871499
Thank you for Ventoy, I just remembered that longtime ago I was using it to try several Linux distros! I didn't knew that it could work also for Win, I will just try right now. Thank you also Enthousiast, alas I can't ignore this message, because each time I had this message; the installation of win10 failed. I have disconnect all my external units now, thank you for the recall!
This rufus message is not from windows, it is rufus acting up, windows should install fine, with secureboot disabled anyway.
OK, I'm gonna try again now, with the MVS isos, and with secure boot deactivated, I understand that this warning from Rufus is to take with a big grain of salt, so I will try and see! I have of course to disconnect everything now, will report later if I have any positive result!
19044.5796.1.13 ? 1--Did you mean the latest build 19045.5796 ? there is no 19044.5796 build on microsoft site Only 19045.5796 2--latest build of loT 2021 is 19044.5737 Does the updates above create 19044.5737 build?
Please read this [DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release], why do people don't take time to read ?
if you find 19044.5796 on https//learn.microsoft.com/en-us/windows/release-health/release-information i give u coffee pleas read my question more then one time [DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]
(IoT) Enterprise 2021 LTSC is and will always be 19044 ALL updates are 19041 based and with the 21H2 EP it is 19044, as 2021 LTSC is and with the 22H2 EP it will be bumped to 19045.