New
#40
Talking about an odd time to push an out-of-band CU, right in the middle of the night last night. However, no issue so far after installing it.
Cumulative Update KB4345421 Windows 10 v1803 Build 17134.167 - July 16
-
-
New #41
A question please. When cumulative updates such as this appear are they incorporated into the 1803 d/load or are they a required update to 1803? I ask because I've had to revert the one 32 bit system here to 1709 because 1803 wrecks its LAN connections, and obviously I'm hoping a cumulative update will rectify this. However this is all a bit tedious even without having to update 1803 first in order to find out. TIA
-
New #42
Each cumulative update includes all previous fixes. The 1803 install media downloaded by the Media Creation Tool installs a base version which you then update with the latest cumulative update. The base version has recently been revised from 17134.1 to 17134.112.
Each version has its own cumulative updates, so fixes for 1803 that are applicable to 1709 will be incorperated in the 1709 cumulative updates.
Your LAN problems are more likely to be down to changes in the defaults for networking settings, particularly in the way the deprecated SMB1 is handled. You may find that 1803 will work for you if you turn on SMB1. Network Discovery is another setting you may need to adjust. See if these threads help.
1803 disable finding computers by name? - Windows 10 Forums
Computers can't see each other after upgrade to 1803 Solved - Windows 10 Forums
-
New #43
Just noticed this patch.... Oh well, downloaded and all is well... Exept OneDrive asks to log in again, when I'm already being logged in... Just resetted my PC and all is well again. Must be a bug of some sort...
-
-
New #45
Following this update I can not seem to get rid of the dreaded:
Several restarts and a disk clean and its still there.
-
New #46
-
New #47
No I haven't done a manual check... let me try.
-
New #48
Ah, nice one. Yes that seems to have zapped it. Thanks :)
-
-
New #49
As the name implies CU is just that. It contains all the previous fixes, meaning if they were already applied, only the new ones would come down to your system. Don't expect Microsoft to fix your LAN problem with a new CU, unless the problem is widespread and known to be on Microsoft's end.
With that said, I don't think it is a good idea to turn SMBv1 back on since there is a flaw in its function. That's why MS has disabled it. I also think that you should put your system back to 1803 and try to fix network settings' issue. I had the same problem last week and the way I fixed it was with the help of the following tutorial:
https://www.drivereasy.com/knowledge...-found-solved/
Notice that you don't have to go through all the steps. My problem was fixed right before step 4:Reset TCP/IP. At first, I was not really confident that this tutorial would fix my issue. Amazingly, it did.
Quote
Related Discussions
