McKnife
asked on
Win10 1803 systems are not offered the 2018-05 Cumulative updates
Win10 1803 systems are not offered the 2018-05 Cumulative updates (KB4103721) when connected to WSUS (here: wsus on 2012 R2, but it should not even matter)
As https://social.technet.microsoft.com/Forums/en-US/44fc841c-3e39-49c1-b1a0-a633c76e2796/win10-build-1803-clients-monthly-cumulative-update-not-offered-may-2018-kb4103721?forum=winserverwsus outlines, the new windows build refuses to work with WSUS (like it has happened before with server 2016 and Win10 1607).
Please reproduce and upvote the technet thread, so Microsoft becomes aware.
Points to anyone who takes the time to reproduce.
PS: 1709 Build 16299.402 (if you have it) is unable as well.
As https://social.technet.microsoft.com/Forums/en-US/44fc841c-3e39-49c1-b1a0-a633c76e2796/win10-build-1803-clients-monthly-cumulative-update-not-offered-may-2018-kb4103721?forum=winserverwsus outlines, the new windows build refuses to work with WSUS (like it has happened before with server 2016 and Win10 1607).
Please reproduce and upvote the technet thread, so Microsoft becomes aware.
Points to anyone who takes the time to reproduce.
PS: 1709 Build 16299.402 (if you have it) is unable as well.
Thanks McKnife for letting us know...
That update appears to have a bug (May 8, 9 2018).
It installed on my ThinkPad X1 Carbon last night and all was well (I thought).
This morning upon startup there was a Windows Hardware Error (Live Kernel Event). Then after an hour I found my Right Context function (Windows Explorer) would not work. This was an issue with V1709 that Microsoft fixed with Build 16299.309 and later).
I tried to do a Repair Install and it tells me I have the wrong language pack. Repair Install has not failed me up to today.
I uninstalled KB4103721 and I am back to 17134.1. All is well again. I have deferred installation of the update at this point to May 15.
Do not rush. KB4103721 has issues.
It installed on my ThinkPad X1 Carbon last night and all was well (I thought).
This morning upon startup there was a Windows Hardware Error (Live Kernel Event). Then after an hour I found my Right Context function (Windows Explorer) would not work. This was an issue with V1709 that Microsoft fixed with Build 16299.309 and later).
I tried to do a Repair Install and it tells me I have the wrong language pack. Repair Install has not failed me up to today.
I uninstalled KB4103721 and I am back to 17134.1. All is well again. I have deferred installation of the update at this point to May 15.
Do not rush. KB4103721 has issues.
Lots of internet traffic on this KB above
https://www.windowslatest.com/2018/05/09/windows-10-kb4103721-bugs/
https://www.windowslatest.com/2018/05/09/windows-10-kb4103721-bugs/
ASKER
John, it's not a single update. It is all windows updates (the second may update is for flash) and it's with WSUS. Do you use WSUS at your customers? Test it there. Private experience does not matter.
Our very small clients are not using WSUS and we have not yet updated anyone to 17134.48 at this point.
Yes, I saw the flash update also uninstall. And yes I know it was a cumulative update.
Still it is not working for more people than I usually see after patch Tuesday.
Yes, I saw the flash update also uninstall. And yes I know it was a cumulative update.
Still it is not working for more people than I usually see after patch Tuesday.
it's not a single update. It is all windows updates (the second may update is for flash)
I re-updated to 17134.48 earlier this afternoon and this time I had to reinstall the Conexant driver (bad driver older than dirt that Lenovo does not update).
But just now (two or three hours later) Flash updated a second time on both machines. So Flash may have been a bad update.
I re-updated to 17134.48 earlier this afternoon and this time I had to reinstall the Conexant driver (bad driver older than dirt that Lenovo does not update).
But just now (two or three hours later) Flash updated a second time on both machines. So Flash may have been a bad update.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Once I did the second (same) update, all has been well. Yes it is strange what you are seeing. I saw and read your post about Microsoft and WSUS
ASKER
I don't know how it was fixed, but it is.