Cumulative Update KB4493509 Windows 10 v1809 Build 17763.437 - April 9 Win Update

piepowder said:

Avira got back to me. They have a fix. So I uninstalled Avira and installed the new version. no change - the boot is the issue. Windows logo, then black screen, then turn off computer physically, then restart. Works. Tried this process x4. Hence it is still a boot problem. Start up repair in safe mode did not work either. So either Avira have nor resolved teh issue with a fresh install, or, Microsoft has become corrupted. I have replied to Avira in this vein.
Sigh.
Will we have to wait for May's new Windows version?

Possibly it would be a good idea to uninstall Avira completely and relies only on WD +MB free edition for now. You can try to reinstall it after 19H1 stable is rolled out to the public. This way, you would have a good idea whether it's MS or Avira the culprit.

CountMike said:

If any SW would give me as much as 10% of the grief like this one does, I would drop it like a hot potato.

How would I say that I am in 150% agreement with you on that one?.

disabled Fast startup - no change. Interestingly on restart it became un-disabled!
System W10 pro 64 bit V1809 build 17763.379. Intel i3-6100 CPU @3.70 Ghz.

So I get a feeling of that no matter what one does, W10 is reverting to a fixed corrupted state post KB 4493509. Whether that is the consequence of an interaction corruption between AV software and MS software I know not. The issue is the boot.

piepowder said:

disabled Fast startup - no change. Interestingly on restart it became un-disabled!
System W10 pro 64 bit V1809 build 17763.379. Intel i3-6100 CPU @3.70 Ghz.

So I get a feeling of that no matter what one does, W10 is reverting to a fixed corrupted state post KB 4493509. Whether that is the consequence of an interaction corruption between AV software and MS software I know not. The issue is the boot.

Just curious to see what would happen if Avira is completely uninstalled. If the boot issue is still present after that, there are lots of ways to fix it. If not, that would give you the answer to your problem. I am on build 17763.437 one step ahead of you with no Avira and I don't have this issue:



Very important not to forget about a system image backup before, unless of course, you already have a recent one.

Recent Avira vs April cumulative update issue (GUI lockup) manifested itself
- either during AV update
- or during user logon phase, not OS boot phase.
After 3-5 minutes, system continued to work correctly.

Furthermore, there were specific events in System log
Source: avgntflt
Description: TIMEOUT<csrss.exe> C:\Program Files (x86)\Avira\Antivirus\somemodule.dll

None of these symptoms detected in last three days on four physical machines, so I assume the issue is resolved. But it took too long time to be satisfied.

------------------------

On the contrary, piepowder describes his issue, which emerges during OS boot phase (and does not recover itself in some minutes) and continues after recent Avira updates. Besides, he mentions some other glitches of his OS installation; it is not possible to assess Avira's degree of success by running it on diseased system. Furthermore, he never quoted any warning/error fron event logs.

So the problem described by piepowder is most likely sligtly different issue not related to Avira.

The thing to recall though all this began with KB4493509 release

could be anything - MS, AV or both. Currently running a deep scan for Avira. Wiredly on power button - it went straight to start with no boot issue - out of 8 starts.