Windows 10 Creators Update available through the Update Assistant

Ah, I'll bet that was it as I don't have the mic plugged in at present. Well, I'll have to plug in the mic and ask Cortana some questions.

I tried to update my 5 Win10 systems today using UA.

3 of them (Win10 Home) are updated successfully.

The rest of 2 (both Win10 Pro) failed, were frozen at 32% (stopped spinning) for a long time and I had to reset the computers (and they went back to the previous system). I gave 1 of them another try, it failed exactly same.

reddice said:

Libreoffice blurry text is caused by the latest version even in the anniversary edition. It ignores hardware acceleration which I think the newest Windows build does too. However the previous version 5.3.1 the fonts look normal even with the latest creators update.

It's recommended not to use version 5.3.2 while 5.3.1 is stable.

The latest "fresh" version of LibreOffice, recommended for technology enthusiasts.

The described difference is between Fresh and Still, I'd call Fresh as a BETA version, could have problems.

When I run Update Assistant on one of my Windows 10 Pro x64 machines, it refuses to update to CU, claiming that this machine cannot run Windows 10. The red item in the list says that the machine does not support UEFI boot.

That machine is indeed currently configured for BIOS boot (even though it does support UEFI, if I change the BIOS setting).

So, what is going on here? Will the CU make UEFI boot mandatory? Or is it just a peculiarity of Update Tool (while regular update on April 11 will support BIOS boot as well)?

AndreyT said:

That machine is indeed currently configured for BIOS boot (even though it does support UEFI, if I change the BIOS setting).

Mine too!
Even if machine supports UEFI, the upgrade was made in BIOS mode and libre Office 5.3.2.2x64 runs normally as in Linux.

There most be something that you do wrong?

MikeMecanic said:

There most be something that you do wrong?

What can I possibly do wrong, if the only thing I do is download and run the Upgrade Assistant?

AndreyT said:

What can I possibly do wrong, if the only thing I do is download and run the Upgrade Assistant?

If an installer does not bring you to a fluent desktop environment (same for an upgrader), meaning that data transfer was ain't set properly, then the installer failed to do the work.

Here, the app is an upgrader (similar work), a brand new one, that re-writes the code name in 35 minutes (best RS-2 achievement and best Upgrader ever made by MS) refuses to go to work.

Then, there is something wrong with your machine? You're the only one that can fix it. Think about it? Are you getting CU normally, do you have side effects, does your machine health in good condition... The premise for a successful upgrade is a healthy machine, is it the case? Is there a parameter(s) that may cause this? Think about it!

The solution is on your side.

MikeMecanic said:

If an installer does not bring you to a fluent desktop environment (same for an upgrader), meaning that data transfer was ain't set properly, then the installer failed to do the work.

Um... This just doesn't ssem to make sense to me. The updated "fluent desktop environment" is out of question since the Upgrade Assistant refuses to even start the update process. The machine does not pass the pre-check stage.

I, of course, run it from under my current Windows 10 "fluent desktop environment", which continues to work perfectly.

MikeMecanic said:

Then, there is something wrong with your machine? You're the only one that can fix it. Think about it? Are you getting CU normally, do you have side effects, does your machine health in good condition... The premise for a successful upgrade is a healthy machine, is it the case? Is there a parameter(s) that may cause this? Think about it! The solution is on your side.

Firstly, I'm not asking for a solution yet. I don't need one at this point. All I'm asking if there are any new UEFI-related pre-requirements in CU version.

Secondly, vague musings about "helathy machines" is not exactly the best path to take here, considering that I do have a rather specific error report from the pre-check stage: it says clearly and explicitly that it does not like something about my UEFI. I'll wait till April 11 rollout and see if it is going to be any different.