Thanks.. good to hear. I've yet to pluck up courage (or be bothered enough??) to try again, having been busy with other things. I intend to follow my usual policy of not upgrading
a. Until Aeroglass is compatible
b. The first major update has been released...
Thanks.. good to hear. I've yet to pluck up courage (or be bothered enough??) to try again, having been busy with other things. I intend to follow my usual policy of not upgrading
a. Until Aeroglass is compatible
b. The first major update has been released...
It's an MBR system, so the same four it had since it was an OEM Win7 machine. The recover partition after the initial free upgrade to 10240 was 845MB, and has remained that size through all subsequent upgrades.
My test machine is also MBR. As I mentioned in post #16 all four partitions were already used for other things when I upgraded it to Win10. It has no recovery partition, rather the upgrade put a protected/hidden recovery folder on the C: drive instead - has the same files and does the same job as a recovery partition. That too upgraded successfully to 1709.
Solved when I discovered the CU viewed my SSD as Disk 1, whereas the AU viewed it as Disk 0. Quite unexpected.
I clean installed the AU and replaced the Windows partition with that from my CU build.
Thanks to great efforts by all!
Great news!
I hate unsolved mysteries, especially in IT.
Even if you can find a 'cure', you can't trust the fix until you know the cause.
I know this is an old thread, but I found myself in nearly the exact position dalchina was in. My system would boot up fine, but if I tried to launch any of the tools from the recovery environment, my system would reboot to a logo with no spinning dots and then a blank screen would appear. If I left it there for a few hours the system would just shut down.
It wasn't the end of the world because I could launch them from installation media if I needed to. But then it came to pass that I needed to do an in-place repair install and I was getting the same errors as he did. So I tried his solution, but it didn't work for me. I was working with a version 1803 image and installation media and I didn't have any backups that were more than two months old, so I didn't have anything Pre-CU to work with. After 6 more hours of research and testing, I finally stumbled across what worked for me.
I had 4 hard drives and an SSD that my image was booting from, all configured as GPT, so I had my BIOS configured as UEFI only. I didn't have secure boot enabled, so I thought this couldn't be a problem. But just as a last ditch experiment, I switched it to Legacy + UEFI and BOOM! That solved all my problems. Everything in the WRE worked and I was able to complete the repair install. I can keep it in exclusive UEFI mode for normal use, but if I need to perform any actions where windows has to boot into WinPE, I have to open it up to Legacy as well.
It took me almost a week of searching and failed fixes to find this thread that dealt with my specific symptoms and I tried every fix suggest in this thread. I doubt we are the only two who have been going through this. So if anyone else in the same boat gets this far, I figured it would be a good thing to share what I found in case it could be helpful.
Quote
