This definitely confirms that 18362 and 18363 share servicepack build numbers, but it makes me wonder about where the servicepack build number will go from 10022? Will there be cumulative updates beyond 10022 with 18363 or will they have to be rolled back at some point.
So my thinking is that I should probably not apply kb4517245 (the enablement package) to go from 18362.10022 to 18363.10022. It is probably best to stay with 18362 until update Tuesday. Do you (Enthousiast) have an opinion on this? Has anyone else applied the enablement to 18362.10022?
Just stay in the slow ring and when msft decides to create the option to switch to the releasepreview ring or directly to the retail release ring you can switch.
Nothing with the build nr only that Windows Not updates itself within the period of time after setup. Removed it from the post.
That is what I was hoping you would say because I was thinking that switching rings might cause problems. Cheers!
my windows updated itself it to .388 automatically. i don't see any problem with search or start menu. what is the bug about?
Agreed, I don't care for this either but when I have a client call or file a support ticket i just give this solution. I have also read that this is only a problem for users of the Home/Home SL editions. I hope that MS reverses this in an upcoming update.
They didn't reverse this since 1803 Home (+SL) | (i didn't bother to test 1709 or lower). Solutions: - Disconnect LAN physically - Entering 1111111111 (or an incorrectly formatted email adress) - Disable the adapter
How difficult is it to disable or unplug the internet? I always install disconnected from the internet. In case of Windows 10 it is also better not to install the video driver automatically, a driver probably outdated and without the control panel. Although I think that the option to create a microsoft or local account should be highlighted equally during the installation even when connected.