It doesn't look like a flop. It acts like one. It IS one, but as I said, once major bugs are fixed and minor bugs don't melt hardware and/or don't cause enough brain damage for someone to think that they could and report it on the news, the next update is good. I endorse it - that means a LOT.
Do not assume that with such a serious issue, like the file deletion bug was, they will be done in a few days. And, if you remember, MS was at least before Oct 2 totally silent as well.
I have a serious problem with the lack of any information out of Redmond. I am using 17763,104 without any problems but I would like to get on with this. What does it take , I get no response from anyone.
I encountered the same issue a couple of days ago, I also found that not checking for updates did not help. Finally I was able to get the update to install by changing the default gateway on my network connection so the install program could not phone home to Microsoft to check for updates, it took a while attempting to check for updates but then the update installed as normal.
You won't get a response until they release a statement publicly. If it's working fine for you, why worry?
When using Check point capsule as the VPM provider (from microsoft store) on any build of 1809 Windows 10, the operation times out. Anyone else experience this? Is there any work around other that reverting to an older build of windows 10?
New CU (17763.107) available: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-334#post-1477265
All 1809 updates are RP and Slow ring at the moment. Non insiders can use dism to integrate/install them.
To Add updates Via dism you do It this Way Create Folder in C:\ & name it update then copy the SSU KB4465477 to it then run with CMD (Admin) and install dism /online /add-package /packagepath:"C:\update\windows10.0-kb4465477-x64.cab or x86 Then delete KB4465477 in update Folder & copy in KB4464455-x64.cab or x86 Then run this in CMD (Admin) dism /online /add-package /packagepath:"C:\update\windows10.0-kb4464455-x64.cab or x86 If successful you will be asked to reboot. You should now have 17763.107 Hope this Helps TECHNOMAN