Windows 7 customers really need to be on the lookout for a handful of, uh, challenges this month, while the Win10 1803 trail of tears continues and Win10 1709 finally looks pretty solid.
The Win7/Server 2008R2 network card bugs continue

First, what's promising. If you installed last month's Win7/Server 2008R2 patches plus your network connections didn't go kablooey, you're almost undoubtedly Alright to proceed keeping this month's patches.

By contrast, if you've been waiting to fit patches on your own Win7 or Server 2008R2 machine, you have to aware of a bug that Microsoft has acknowledged. It absolutely was introduced by a patch back in March, while using KB articles, and hasn't been fixed yet:

Symptom: Careers issue with Windows and third-party software that may be related to military services weapons file (oem<number>.inf). Due to this issue, in order to apply this update, the network interface controller will prevent working.

Workaround: 1.To look for the network device, launch devmgmt.msc; it may possibly appear under Other Devices.

2. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes on the Action menu.

a. Alternatively, install the drivers with the network device by right-clicking this device and selecting Update. Then select Search automatically for updated driver software or Browse my computer for driver software.

That's a bizarre, convoluted few steps. Microsoft still hasn't confirmed which third-party software is at fault.

If you're worried that installing this month's updates will clobber your network interface card, grab a full backup before installing the updates. You can even take @GoneToPlaid's advice and edit certain registry entries at the start.
Windows Defender updates have dry up

Older Win7 machines don't get no respect.

First, we Microsoft's decision to complete support for Pentium III processors - an undocumented change accompanied by doctored KB articles that hide the promises possess made. The Microsoft blogosphere responded possessing a yawn: Even though Microsoft repeatedly promised so you can use the processors, they're really old (vintage 2002). You shouldn't be running Windows on old processors anyway.

Now there's strong evidence that Windows Defender updates aren't escaping. Günter Born delivers the details on his Born City blog, and Vess Bontchev confirms on Twitter:

Windows Update don't updates Windows Defender on Windows 7 machines, yo. Last such update was on June 18. Nothing changed within my end firewall- or installation-wise. It's Microsoft's doing.

Just like the Pentium III, Windows Defender is ancient technology, a part of the original Windows 7, and long since superseded among the (free!) Microsoft Security Essentials, which does much more than Defender. Many older Win7 machines still run Windows Defender, though, and although updates are getting released by Microsoft, they somehow aren't making it through. Speculation has it that Microsoft's servers are broken.

The moment you apply Win7 updates this month, make sure if you have Windows Defender enabled and, if it is, get Microsoft Security Essentials.
Windows 10 version 1803 still ain't ready for prime time

If you're stuck in Win10 April 2018 Update - the notoriously buggy version 1803 - really want to get last week's latest cumulative update, KB 4284848. Slumber a servicing stack update, KB 4132650, that you just simply only need to jiggle even if you manually install updates.

Here's what gets me about 1803. Microsoft declared it to be ready for business deployment five weeks ago. However you pick up people who benefit Windows everyday, it ain't necessarily so. Exactly the same experts who tout why people love 1803 (of which there aren't many, if any) will come with up with statements like "After I installed this month's Surface firmware patches, 1803 is suddenly usable" and "The latest 1803 patches finally fixed so-and-so."

1803 isn't ready for prime time. If you need to beta-test 1803, go right ahead, but bear in mind that you can roll it back, should you so choose so within Ten days of installing it. Seems as if the only method to avoid better yet . Win10 machine pushed to Win10 version 1803, is to the metered connection kludge with wushowhide, when i discuss in The right way to block the Windows 10 April 2018 Update, version 1803, from installing. Besides, Pro/Enterprise users should set the feature update deferral (Step 3 in that discussion) to One year.

I don't believe if you'll the Ad Duplex advice that 78% of all Windows 10 PCs are running version 1803. Yet the squeeze is on. 1703 and 1709 are usually relatively stable. Win 8.1 remains the most stable Windows considering all of - most likely because Microsoft isn't hoping to "fix" it as almost as much as the others.
Office

Susan Bradley's Master Patchlist signifies that the June patches look clean, even so the official Fixes or workarounds articles for Office include many specific problems but some possible solutions.
Update

Made ready to take a chance on destroying your NIC? Here's what do you do. The patching pattern must really be familiar to the majority of you.
Step 1. Come up with a full system image backup prior to a install the June patches.

There's a non-zero chance that this patches - even the latest, greatest patches of patches of patches - will hose your machine. Best to have a backup that you're able to reinstall despite that your machine won't boot. This, on top of the usual significance of System Restore points.

There's lots of full-image backup products, including no less than two good free ones: Macrium Reflect Free and EaseUS Todo Backup. For Win 7 users, Should you aren't making backups regularly, take a look at this thread started by Cybertooth for details. You have got good options, both free and not-so-free.
Step 2. For Win7 and 8.1

Microsoft is blocking updates to Windows 7 and 8.1 on recent computers. When you're running Windows 7 or 8.1 with a PC that's a whole year old or less, refer to the instructions in AKB 2000006 or @MrBrian's evaluation @radosuaf's method to ensure that you can use Windows Update to become updates applied.

If you've already installed any March, April or May updates, your network interface card really need to be immune to today's slings and arrows. Yet if you haven't been keeping up on patches, investigate discussion contained in the "Win7/Server 2008R2 network card bugs continue" section above to shield yourself.

If you're very anxious about Microsoft's snooping with you and want to install just security patches, realize the privacy path's becoming more difficult. The existing "Group B" - security patches only - isn't dead, but it's now not within the grasp of typical Windows customers. Once you insist on manually installing security patches only, do as instructed in @PKCano's AKB 2000003 and be aware of @MrBrian's ideas for hiding any unwanted patches.

On most Windows 7 and 8.1 users, I suggest following AKB 2000004: Learn how to apply the Win7 and 8.1 Monthly Rollups. Find that some or the various expected patches for June probably won't show up or, if and when they do pop up, may not be checked. DON'T CHECK any unchecked patches. Unless you're very sure of yourself, DON'T GO LOOKING for additional patches. In that way thar be tygers. If you find yourself going to install the June patches, accept your lot in their life, and don't confuse Mother Microsoft.

You might like to minimize Microsoft's snooping nevertheless install the majority of the offered patches, cover the Customer Experience Improvement Program (Step 1 of AKB 2000007: Turning off the worst Windows 7 and 8.1 snooping) prior to when you install any patches. (Thx, @MrBrian.) At the same time KB 2952664 (for Win7) or its Win8.1 cohort, KB 2976978 - the patches that so helpfully allow you to upgrade to Win10 - uncheck them and spread your machine with garlic. Challenge driver updates - you're more appropriate off keeping them from a manufacturer's website.

After you've installed the newest Monthly Rollup, if you're focused on minimizing Microsoft's snooping, tell you the ingredients in AKB 2000007: Turning off the worst Win7 and 8.1 snooping. Realize we don't really information Microsoft collects on Window 7 and 8.1 machines. But I'm starting to believe that information pushed to Microsoft's servers for Win7 owners is nearing comparable to that pushed in Win10.
Step 3. For Windows 10

If you're running Win10 Creators Update, version 1703 or version 1709 (my current preference), and you also want to remain on 1703 or 1709 as well as never get sucked to qualify for the 1803 pre-release vortex, follow the instructions here to ward off the upgrade. As expected, all bets are if Microsoft, uh, forgets to honor unique settings.

Remember: You need to avoid 1803, don't click "Check for Updates" until you've applied all the precautions submitted to this article, including running wushowhide. Should forget, you'll probably be tossed in the seeker heap and shuffled to 1803 land.

If you're running an earlier version of Win10, you're basically for your self. Microsoft doesn't you anymore.

You probably have trouble obtaining the latest cumulative update installed, always make sure that you've checked your antivirus settings and, if all is well, run the newly refurbished Windows Update Troubleshooter before inventing new epithets.

To gain Windows 10 patched, see the steps in "8 steps to connect Windows 10 patches sort of a pro."