At minimum the really bad bugs, created by "security" patches earlier this year, have been fixed. The problems that remain dwell in the dregs - improbable to bite, but worth knowing about if perhaps something suddenly goes bump at night.

And if you're using Win10 1803, you must ask Microsoft into an increase in combat-duty pay.

The Win7/Server 2008 R2 patching threat

Remember when Win7 was relatively stable? OK, OK; "stable" can be described as relative term that's unlikely in order to use to any type of Windows, nonetheless know what After all. Win7 and Server 2008 R2 already went through a months of issues networking all together, and apoplectic network interface cards right away.

This month's problem (which happens to be different from happens to be two months' bugs) involves a negative .inf file. If you get bit, you don't see some of those completely inscrutable error messages ("CredSSP encryption oracle remediation" anyone?). Instead, your network card just dies. Kerplop.

Microsoft says it's an obstacle in the May Win7 Monthly Rollup doc, KB 4103718:

Symptom: We have an issue with Windows having a third-party software that is correlated to a missing file (oem<number>.inf). That's the reason issue, as soon as you apply this update, the network interface controller will stop working.

Workaround:

1. To buy the network device, launch devmgmt.msc; it may well appear under Other Devices.

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

a. Alternatively, install the drivers for your network device by right-clicking smartphone and choosing Update. Then choose Search automatically for updated driver software or Browse my computer for driver software.

Which must rank among the list of most convoluted instructions Microsoft has ever published. As a minimum, one of the most convoluted instructions this month. Keep in mind Microsoft tells us there's issues with third-party software, but doesn't deign to enhanse us which third-party software.

If, after installing this month's Win7/Server 2008 R2 Monthly Rollup KB 4103718 (or probably the Security-only patch KB 4103712), your network interface card fails, you can use Microsoft's steps to get going again. Once you're back online, take Susan Bradley's advice:

visit the property owner of your computer or use the vendor on the network card increase both your bios and network drivers from the vendor's web site.

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 - you need the latest cumulative update applied, KB 4100403. Prior to you do that, think. Because you "up"graded to 1803 less than 10 days ago, it's still all to easy to roll directly back to your previous version: Start > Settings > Update & security, within the left choose Recovery. Under Return to the previous sort of Windows, click Get started with. Click through Microsoft's warnings again (and over and over) and finally click Buzz Off, I expect my old Windows back. As well as the functional equivalent. Once you've rolled back, ensure that you take the necessary precautions to hold on to Microsoft from forcing you directly to 1803 again.

Speaking about forced upgrades, Microsoft is actively on the search for folks who were upgraded to 1803 even though they had Win10 1709 set to defer updates. Those with the temerity to click "Check for updates" - you seekers - does not need to apply.

It makes no difference … those of you who happen to be convinced that 1803 now functions with half of all Win10 PCs here is a lesson in lies, damn lies and statistics. Ed Bott over on ZDNet provides a great takedown within the AdDuplex numbers that fueled the clearly ridiculous assertion. 1803 hasn't bought out the Win10 universe. As much as, not yet.

Win10 versions 1703, 1709 willing to roll

The bugs introduced earlier from the month are fixed. In my opinion ,.

My production machines still exist on 1703, even so I get an extra couple of hours, I'll probably relocate to 1709. (Yes, I downloaded and saved a copy of the Win10 1709 ISO file back even though it was available. Make a few moments one, have a look at Ed Tittel and Kari Paajolahti's article in Computerworld.)

My partner and i it's quite remarkable that Windows 8.1 carries on to stand out for the reason that most stable type of Windows available.

Office

Susan Bradley's Master Patchlist shows we're basically eager to roll, although the official Fixes or workarounds articles for Office include many specific problems while some possible solutions.

Windows 7/Server 2008 R2

Able to take a chance on damaging your NIC? Here's what direction to go. The patching pattern must be familiar aspiration they hope to of you.

Step 1. Build a full system image backup till you install the May patches.

There's a non-zero chance where the patches - including latest, greatest patches of patches of patches - will hose your machine. Wise to have a backup so that you can reinstall if your machine won't boot. This, independent of the usual depend on for System Restore points.

There are several full-image backup products, including at minimum two good free ones: Macrium Reflect Free and EaseUS Todo Backup.

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 in a PC that's pa old or less, refer to the instructions in AKB 2000006 or @MrBrian's analysis @radosuaf's method to you should can use Windows Update to be updates applied.

If you're very concered about Microsoft's snooping providing you with and want to install just security patches, remember that the privacy path's acquiring difficult. This "Group B" - security patches only - isn't dead, but it's now not within the grasp of typical Windows customers. If you decide to insist on manually installing security patches only, follow the instructions in @PKCano's AKB 2000003 you can also be aware of @MrBrian's tips on hiding any unwanted patches.

For some Windows 7 and 8.1 users, I suggest following AKB 2000004: Simple tips to apply the Win7 and 8.1 Monthly Rollups. Remember that some or the expected patches for April may not show up or, when do arrive, may not be checked. DON'T CHECK any unchecked patches. Unless you're very sure of yourself, DON'T Go searching for additional patches. This way thar be tygers. For everybody who is going to install the May patches, accept your lot in your everyday life, and don't wreak havoc on Mother Microsoft.

If you desire to minimize Microsoft's snooping trip install every offered patches, go out the Customer Experience Improvement Program (Step 1 of AKB 2000007: Turning off the worst Windows 7 and 8.1 snooping) prior to deciding to 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 help you to upgrade to Win10 - uncheck them and spread your machine with garlic. Be wary of driver updates - you're superior off obtaining from a manufacturer's website.

After you've installed most up to date Monthly Rollup, if you're set on minimizing Microsoft's snooping, run through the procedures in AKB 2000007: Turning off the worst Win7 and 8.1 snooping. Recognize that we don't are aware of what information Microsoft collects on Window 7 and 8.1 machines. But I'm starting out to believe that information pushed to Microsoft's servers for Win7 owners is nearing equivalent to that pushed in Win10.

Step 3. For Windows 10

If you're running Win10 Creators Update, version 1703 (my current preference), or version 1709, the Fall Creators Update, and you simply want to continue to 1703 or 1709 without get sucked directly into the 1803 pre-release vortex, follow the instructions here flexible terms with the upgrade. Undoubtedly, all bets are if Microsoft, uh, forgets to honor the liechtenstein settings.

Remember: If you'd like avoid 1803, don't click "Check for Updates" until you've experienced all the precautions submitted to this article, including running wushowhide. Should you forget, perhaps you are tossed while in the seeker heap and shuffled off and away to 1803 land.

If you're running beginning version of Win10, you're basically on the. Microsoft doesn't support you anymore.

If you have trouble buying the latest cumulative update installed, make it a point you've checked your antivirus settings and, if get up, run the newly refurbished Windows Update Troubleshooter before inventing new epithets.

To possess Windows 10 patched, evaluate the steps in "8 steps to put Windows 10 patches for a pro."