![]() ![]() TBH I'd move away from 1607 as support ends in April. Looks like KB4049411 may have been pulled but it hasn't been superseded. It would not allow me to sign in to my Microsoft account after it updated. I have already had to use the create disk twice because this update screwed up my computer so bad. It installs other updates but not build 1511. So you have to approved say the 2019-01 CU and SSU within 4 weeks of patch Tuesday/Wednesday otherwise you fall behind and risk older updates say from Nov/Dec being superseded.Īfter the SSU is installed a full Software Updates Cycle must happen for the CU to installed. Every time I try to install build 1511 it says some elements could not be installed. If the SSU is not installed the WU Agent will not install the CU. ![]() This gets updated quite regularly and if you remove updates from SCCM once they are superseded you must deploy the latest. If not check that your deployment that is targeting the PCs has the SSU for 1607/1703/1709/1803/1809. Get-WmiObject -Class Win32_QuickFi圎ngineeringĬheck that for example on 1709 KB4477136 which is the SSU is installed. This helps if you've set updates to be hidden in the Software Center. Get-WmiObject - Class " CCM_SoftwareUpdatesManager " - Namespace " ROOT\ccm\ClientSDK " - ErrorAction Silentl圜ontinue - Verbose Check no updates are pending. Now for audit purposes I need to be able to verify that this patch is successfully installed on the servers but when i go to installed updates it does not. On a PC where it not getting al the updates run this
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |