New
#130
Why would MS say end of November unless it was proving to be a bit tricky?
Whilst the bug is irritating, it has been around since 1803 and is not a showstoppeer. If we wait for every bug in the known universe to be fixed, 1809 would never be released.
If in December, it has not been fixed, then complaining about it is valid.
Funny how people moan MS do not keep them informed, and when they do, people still moan.
I talked about that in this comment.
I think it's more a case that MS only confirmed it as a Known Issue in both 1809 and 1803 less than a week ago. Note the date...
Cumulative Update KB4462933 Windows 10 v1803 Build 17134.376 - Oct. 24 - Page 5 - Windows 10 Forums09 Nov 2018 at 17:33
UPDATE:
New known issue added for KB4462933 in first post.
Is there any downside to updating through the iso? I know they said to wait for it to roll to your updates but is that just so everyone might not get another problem all at once like last time?
Hi, given posts #45, #112 and #132 indicate nothing's been fixed (can anyone refute that? I'd be happy...), what has MS been doing all this time?
They issued a communique about their extensive test regime. If nothing has been fixed (bar perhaps the data deletion problem), can MS be regarded as reliable, responsible, or at all responsive to comments via the Feedback Hub, for example?
Rather disappointing to have to scan so much to find so little said about bugs noted in the previous release.
The CU today is generally security fixes. Next week we will likely see another CU with a whole whack of bug fixes.