Don't delete the temp folder and download the exact same build, it will only download the file with error.
I continue with start menu bug. I updated to 17763.1 from my current windows version. A first restart, start menu works OK, and same at second restart. But at third restart my start menu config dissapears: it shows a "reseted" start menu. But this is not all: if I change "start" options or "start folder options" simply it does not work. Example: I chose to show documents folder in start menu, and it do not show at start menu. I installed a clean 17763.1 version inside a virtual machine and start menu works OK. It appears to be a bug updating to 17763.1 from current version of windows. Any solution to this?
I can't see what you are doing now, you can copy the txt and paste it here in code tags. But i think it's the question about the download folder already existing, then press [P].
Upgraded from 17758.4 on a live system with multiple accounts, went well. Pt-pt language pack and optional features auto-downloaded/install fine, but the UI pt-pt language pack atm is unfinished (I have it for one user). Many elements on Settings are still shown in En-us, but his has happened in the past, where MS updated it later. Edit: Integrating the languagepack-package esd from another 17763.1 uup download folder in pt-pt to the en-us install fixed it.
17763.1 is the rtm i doubt on coming this Monday they have a new build Tuesday be sign off if no major bug like the April update
Finally a solid release, I was stuck at desktop after a boot in 1709 for about a min, in 1803 it was about 2 mins, 1809 does not suffer from this bug anymore, desktop is accessible ASAP.. 1809 is fast as hell, everything opens instantaneously. Good job MS. Though by default it had 142 processes, I am sure they are all needed, but I still got it down to 44.
I can confirm the bug related to bad reading (value ?) , into the task manager at least for the CPU load report.
17763.1 Setupact.log contains build identification as: "Target Build Signature Type: 4. RTM_OR_PRODUCTION_SIGNED". But in RS4 builds, the same identification was present in 17128, 17133, 17134. Thus it is still possible that another 1776x build may appear next week.