|Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору|
| Создаём исошник на базе 1903. Другие не пробовал. |
Интересно, конечно, но... может Macrium не зря использует более старую версию WinPE10_1709? ... таки Жираф большой, ему видней...
Кстати, я пару дней назад задал вопрос о совместимости программы бекапа с NVMe SSD на «забугорном» форуме Macrium и получил довольно интересный и содержательный ответ … кстати, там есть и про “WinPE10_1903 вместо WinPE 10_1709” :
“… It would be the same as if you had been replacing a failed SATA disk. You would run the restore and move on. You can even restore an image from a SATA disk onto an NVMe SSD and vice versa, although that typically requires you to run Macrium ReDeploy, which isn't included in the Free version. Again, you're overthinking this.
There are are only two potential stumbling blocks that I've seen:
If your Windows environment was on a Samsung NVMe SSD and you had the Samsung NVMe driver installed, and then you restore it to a different Samsung NVMe SSD model -- but still a Samsung SSD -- someone on the Macrium forums had trouble getting that to work. Apparently Samsung has different variants of its NVMe driver for each model, and I think even ReDeploy wasn't able to fix that. Or maybe they were running Free and didn't have it. I can't remember. Since they still had their old setup, they just uninstalled the Samsung NVMe driver, captured a new image, and restored that to the new successfully. Then they reinstalled the Samsung NVMe driver on the restored system. I'm not sure what would happen if your Windows environment had a Samsung NVMe driver loaded and you restored to a non-Samsung SSD.
I tend to stick with the Microsoft NVMe driver.
The other challenge is that the RAID drivers on newer AMD motherboards seem a bit complicated. There are multiple components that have to be loaded in a specific order, and getting that working properly in Rescue can be an issue. But that's not an NVMe issue; that's an AMD RAID issue...."
You know that WinPE 10 has version 1709. I downloaded this version in 2020 and compared it with the checksum version of 2021. This version has not been updated for a long time.
"... Macrium was using WinPE 10 1607 before they moved to 1709, and the reason was that 1709 added support for multi-partition flash drives, which was useful for Rescue Media flash drives. Yes I'm well aware that there have been multiple releases since then, but I don't think any of them have added any features that are relevant to Reflect. They might have more drivers built-in, but Rescue Media can already deal with adding drivers. If you really want to use the latest release, if you actually move to Windows 10 you'll be able to do that by building your Rescue Media with WinRE, which will use whatever WinRE kernel your system uses. But newer is not always better. Microsoft has had WinPE/RE releases that contained bugs, so if you rush out to install the latest release and update your Rescue Media to use it, you might find that your Rescue Media doesn't work properly. The initial release of WinPE/RE 10 1809 had a bug that broke driver loading, for example, and then Microsoft recalled Windows 10 1809 entirely before releasing it again a few weeks later. So I personally have no problem running an older release that Macrium has tested. And if newer versions don't add any value, then I'm just as happy that Macrium spends time on other improvements to Reflect. I got over wanting to be on the newest versions of things "just because it's the newest" a while ago…”
Вот такие пироги с котятами…
некоторая проблема совместимости имеет место быть с SSD Samsung NVMe, но решается это довольно легко: перед бекапом удалить драйвер NVMe от Samsung и оставить официальный от Microsoft.
После бекапа драйвер NVMe от Samsung можно вернуть обратно.
Всего записей: 235 | Зарегистр. 17-05-2017 | Отправлено: 00:12 31-03-2021 | Исправлено: Jacky003, 00:19 31-03-2021