oh okay will do that tonight, BTW, is there any new thread or op created after this? Asking this bcz am not seeing much discussions /comments here for last one/two days.
All this would not happen if Microsoft continued with the good old Windows 3-year release scheme, and not trying to be rolling release like Linux.
Have no idea. I use the Pro version. My feeedback about cortana crashing got 3 upvotes and a comment confirming it's also happening on their PC, so at least I know I'm not alone. I have a feeling few make a habit in observing their Reliability History and monitor their Event Viewer.
I look at my event viewer everyday just because it is a habit now.... I haven't noticed anything out of the normal yet especially under heavy load but I will investigate.
There are also a lot of feedbacks about the broken wpprecorder.sys which is quite severe as it makes updating to 1809 fail in many cases and it completely breaks the booting from a WinToGo system. Wonder if a cu only will be able to fix all the bugs.
This is a total guess but I would say they want it out by 31 October. Look at the April Update, released on 30 April, the last day of April but it's still April.
Can anyone confirm this script I quoted is a 100% working/proper method to actually do a full offline WIM update from the yanked RS5 to 17763.104? Unless I missed it I don't really see any comments one way or another or any other posts with confidence/backup that it is possible. I keep reading conflicting posts that it is not possible to do a full offline and that the SSU kb4465477 needs to be done online. I just want to take the RTM 1809 and patch it with the high priority patches MS put out to prevent the data loss. I don't mind doing it online if I must but prefer to integrate if possible which is why I'm asking.
But don't forget that 1809 actually was released Oct 2, so there's likely doesn't exist any "31 oct deadline".. But I may be wrong..
No Ahsan , 17763.104 has still many bugs not fixed in it.. You can have no issues but that does not mean 17763.104 is stable