The blogosphere is awash in reports of issues with this month’ s Win10 1903/1909 Cumulative Update, exceeding 100 reported bug sightings. What’s causing the problems?

The trick every month would be to sift through all of the problem reviews and see if there are any kind of common strings – regardless of whether folks running this part of hardware or that type of software should be especially careful.

I’ ve been looking at the particular reports and I’ lmost all be hanged if I can easily see any pattern, aside from the typical cacophony of random mistake messages and broken techniques. Can you see any typical threads?

We’ re still obtaining ‘temporary profile’ bugs

I’ ve been talking about this with regard to more than 8 weeks .   In some set of circumstances, up to now undiagnosed, the Win10 Total Update installer hits the “ race condition ” upon reboot, with the user returning up in a temporary user profile. That sounds like a lot of hype words, and it is, but the internet result is that the user operates the update, reboots, plus returns to a clean desktop computer, without their desktop provide, while files in their normal folders (such as Documents) have disappeared.

It’ s disconcerting, even though you’ re savvy sufficient to realize you’ ve already been pushed into a temporary user profile. The desktop customizations continue to be there, as are the documents, but they behave as if they are part of a different user.

We even have a report on AskWoody from someone who improved from Win10 version 1903 to 1909, and obtained bit by the same disappearing/temporary profile bug.

Microsoft hasn’ t officially acknowledged the frustrate , although it’ s been reported often times on the Microsoft Answers Community forum and in the Feedback Centre. We still have no idea when there’ s a specific plan or set of programs causing the race condition. Every we know for sure is that the bug’ s still there, and individuals are still waking up after setting up Cumulative Updates to Personal computers with clean desktops plus missing – er, moved – files.

If you get hit using the problem, try rebooting 4 or 5 times – go completely to the point where you’ lso are logged in (with the particular bogus temporary profile), after that reboot again. If that will doesn’ t work, there’ s a tortuous way to manually bringing back your own lost profile described in depth by Shawn Brink on Tenforums .

Lots of installation disappointments

Total Update installation failures are usually as common as Lyrid meteors these days. In most (but not really all) cases, they vanish after a quick run through the particular Windows Revise Troubleshooter .

Sergiu Gatlan upon BleepingComputer reports that will he’ s seen issues with a host of error codes using this month’ s Cumulative Revise:   0x80070bc2, 0x800f0900, 0x80070003, 0x80073701, 0x800f080a, 0x800f0986, plus 0x80070002. It’s a hexacious clutter. In general, the Cumulative Revise installer kicks in, includes one of those errors, then progresses your machine back to the previous pre-CU state.

None of the particular Win10 April security sections are particularly pressing right now (in spite of the three zero-day “ previously exploited” safety holes ), therefore getting kicked back to the particular curb isn’ t especially frightening. Think of the specialist rollback as a practical scam that costs you an hour or so or so of PC period, and a lot of gray hair.

… And lots of Blue Screens

Over the years, we’ ve frequently seen Blue Displays crop up immediately after Cumulative Up-dates get installed. This 30 days, there’ s more than the most common helping of blue. Mayank Parmar at Home windows Latest   said he’ s noticed reports of all of these Azure Screens:

• PAGE_FAULT_IN_NONPAGED_AREA
• CRITICAL_PROCESS_DIED
• ACPI_BIOS_ERROR
• INACCESSIBLE BOOT DEVICE
• MEMORY_MANAGEMENT
• DPC_WATCHDOG_VIOLATION
• Portcls. sys

Which is an impressive list. The major is actually that there doesn’ t appear to be an unifying theme – I can’ t stage my finger at an example of a hardware, or one computer software, or a driver, that’ h triggering the BSODs.

If you get strike with a BSOD and you aren’ t automatically rolled returning to a known good settings, you have to go into Safe Setting and uninstall KB 4549951.

Out, out, damned place

Getting rid of a Win10 patch isn’ t easy: Click Begin > Settings > Upgrade & Security. Click Look at Update History. At the top, click on Uninstall updates. Windows throws you into an old designed Control Panel pane (see screenshot).
Microsoft
From the old Control Panel user interface, you can right-click on the problem patch and choose Do away with.

Exactly where we stand now

I always recommend that you not set up this month’ s spots. While it’ s not possible to say whether this month’ s patching bugs are usually worse than preceding months’ – only Microsoft understands the extent of harm, and it isn’t telling – it’ s pretty apparent that lots of people are having problems.

By contrast, this month’ s crop of safety patches isn’t particularly pushing, unless you’ re working Windows 7, have covered Extended Security Updates, plus you’ re concerned about (yet another) font-parsing bug that will hasn’ t yet caused it to be into widespread exploits.

For now, you have essential things to concern yourself. We’ ll let you know if any kind of credible mainstream threats occur.

We’ re still at MS-DEFCON 2 on AskWoody. possuindo .