|
There are isolated problems with current patches, but they are well-known and documented on this site. |
I have a few machines in a non-WSUS environment, i.e. Windows Update only.
My Server 2016 1607 wants to install July cumulative KB4338814 released July 10:
However, four known issues in that update have been fixed in cumulative KB438814, released yesterday.
The whole point of waiting to update is to avoid buggy patches. So how do I force Windows 10/2016 to skip a buggy patch and download the new one? There is no “Check for Updates” button when an update installation is pending.
Don’t know the answer.
I would start by hiding it and pulled the trick you did a few months back – pull the plug on the Interned till it gives up, hide it with wushowhide, There is a DISM command to cleanup pending (somewhere mentioned in the last month on this site. Run Disk Cleanup and clean up System Files = Windows, DO, etc.
My system is to just try things – not very scientific, but sometimes it works.
If you are just testing why not download from the Catalog and do a manual? Then the other will go away.
@mcbsys as @pkcano suggests the catalogue using, for example wusa.exe C:\kb??????? /quiet /norestart but as I note you cant “Cheat” alas, although no one at @askwoody will say a word, we promise. Not dabbled with 2016 Server. Last Serv. I had my paws on was Win2k so my advice is probably no use hope you get it fixed.
The sequence that seems to work for me is:
1. hide the update in wushowhide
2. disconnect the internet
3. start the updates that are showing and then close “settings”
4. stop the windows update service
5. go back to windows update – I usually find a message there along the lines of “updates couldn’t be installed as your pc was switched off”
6. reconnect the internet
7. check for updates (this should also start the windows update service again)
@mcbsys
Other than wasting time, there is no problem in installing both patches in sequence, with reboot between installations. See my post below for ways to work around the issue of not being able to re-scan against WU/MU.
Even installing the so-called buggy patches is likely not to affect negatively most of the users reading here and this applies to all OSes.
The recently released patches on July 16 are in the category of Updates (which means Recommended Updates) and not Critical or Security Updates.
The originally released patches are the Security Updates and they have not been expired, only somehow hidden or throttled until further research from Microsoft I assume.
Still better to avoid all July patches until the issues are sorted out or at least clarified or unless there are other factors mandating installation, like regulatory compliance.
Yes.
Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
