Thanks for feedback, enjoy your "old" system again!
Please also include the version used next!

Since getting the DUET boot working on my Dell Optiplex 9030 I have now encountered an issue with Windows 10 refusing to update beyond version 1809, Build # 17763.832.

The update installation downloads and begins to update but on reboot, I receive a message "We couldn't complete the updates, undoing changes". The computer then reboots and we are back to square one with the windows update ready to install again.

I cleared out the software distribution folder as recommended but that did not change anything. I received exactly the same message as before "We couldn't complete the updates undoing changes".

Does anyone know whether there is a way to overcome this windows 10 update problem? Much obliged for your assistance.

@WayneFB

Dunno, try to either run the Windows 10 Update Assistant or make an in place update from an downloaded WIN10 ISO image, to do so make an WIN10 USB and while at install select the "keep app and file" option.
If it doesn't work it could mean you made some changes on the recovery partition or system reserved partition got somehow corrupted.

Hello, i managed to move from 3x SSD on RAID 0, TO A Nvme Sabrent Rocket 1TB (clone disk, convert to gpt, create a efi partition and rebuild bcd) now booting windows with duet, but i dont see any speed in loading windows, i get like 1400/1400 mb speed in ASSD benchmark.

Did i miss something!? Do i need any drivers or something?

Regards

System: W3690 @ 4.5Ghz 24gb @ 2000mhz asus p6t deluxe v2 and nvidia rtx 2070 super

To my ears it sounds quite normal. My X58A-UD7 X5670@4,75Ghz 24GB @ 1600Mhz didn't improve in booting time. I can see the difference in Benchmark(s) 2400Mb/s write and 2600Mb/read
BTW nice to hear there's still someone using these old good X58 platforms

@bonet69

That's about right. There is no fastboot option on DUET.
The NVME will just maximize the bandwidth and give better random read\write.

Zitat von PPCnostalgic im Beitrag #545

---

To my ears it sounds quite normal. My X58A-UD7 X5670@4,75Ghz 24GB @ 1600Mhz didn't improve in booting time. I can see the difference in Benchmark(s) 2400Mb/s write and 2600Mb/read
BTW nice to hear there's still someone using these old good X58 platforms

---

I have two 256Gb SM951 AHCI in Raid Zero. I'm using 2 PCIe adapters as well.

That is nice! Have you tried various adapters for compare speed beetwen them?? I think that maybe there are ones better than others...

Yes, I did. Believe it or not I'm using the cheapest Chinese pair, about 6 Euros each, I didn't see any difference with a more expensive Lycom-120 (30 Euros) I also own. The only difference with the Lycom is a pair of pin on the board I used to connect a wire to the front panel for a LED (HD Activity)....

I used Duet to get my HP Z600 workstation to boot Windows 10 from a Samsung 970 Pro NVMe. I did this over a year ago, with Windows version 1809. I have been unable to upgrade windows via the normal methods. The update assistant and running setup from an ISO *almost* works, it gets nearly finished and after rebooting fails with error 0x80070020 - 0x2000A "The installation failed in the SAFE_OS phase with an error during the the PREPARE_FIRST_BOOT operation". So it seems fairly obvious that the failure probably has something to do with the fact that I'm booting a Pre-OS from a USB flash drive instead of from the boot partition of the NVMe. HOW DO I GET AROUND THIS? How can I do an in-place upgrade of my Windows version and keep all my apps and settings? I use my computer for many different things, I have a lot of different software installed, and doing a clean installation in order to upgrade is not a very practical solution.

@Dr. Wizard

Either you search for 0x80070020 error and follow any suggest solution, or find whatever is stopping the installation or do a clean install.
Anyway, once it reboot, after you started the installer, you should remove the OS install media.

Zitat

---

search for 0x80070020 error

---

I have googled the heck out of both error codes and tried all the suggested fixes and then some. I've run the update from a flash drive (and removed it before rebooting), from an ISO, from Windows Update, and from the Update Assistant. I've reset Windows Update, BITS, created a new local admin account, ran file checker, and many other things trying to get around this. And I've been trying to find a way to prevent the rollback when the update fails, all to no avail. I'm pretty tech-savvy and can usually solve my own problems but this one has got me whooped, and not for lack of trying. (But this is a little out of my area of expertise.) It's quite obvious from the log files and even from the error message itself that it is failing because of the funky boot hack we are doing to boot and run Windows from a NVMe drive on a system without native EUFI support. Lets face it, what we are doing here with Duet is not exactly common, and I wouldn't really expect to find a solution to this problem anywhere but here on this forum.
A clean install is what I am trying to avoid since I have a ton of software installed and it takes days to rebuild my machine from scratch. I would really like to find a way to get an "in-place upgrade" to succeed.
Has anyone monitoring this forum managed to do an in-place update of their windows build version while using Duet on a legacy system? How???

@Dr. Wizard

You just follow the normal procedure to do an "in-place upgrade".
If it doesn't work it mean something is interfering, out of it's place or missing from your system, could be a wild range of things.
You should treat it as user-error by software usage. I'd like to provide one command line solution for the issue but that's just not possible by time constrain.
The DUET version provided on the first page doesn't install, poll, remove, interact with/or by any driver, services, file or change in any sort the disk layout on which the OS is running on.
Feel free to boot the affected system with any other available method that best suit your need to resolve the windows update 0x80070020 error.
--
Anyhow, if the "in-place upgrade" doesn't work with an greater version try to do an "install in place" with the same OS version you are running, you should be able repair whatever (since you previously installed) and upgrade next.

Thanks noInk!!
I did an "install-in-place" repair install (even though, according to diagnostics, supposedly, nothing was wrong) of my existing version, 1809, using the 1809 ISO. It completed without a problem. Next, I successfully did an "in-place upgrade" to version 1909 using the ISO. This time I did NOT get the error and it did not roll back the upgrade! Yay!