Windows 10 V1803: (Boot-) issues with update KB4103721

[German]Users who upgraded to Windows 10 version 1803 (April Update) have received the cumulative update KB4103721 as of May 8, 2017. However, some systems have boot problems or other bugs. Here is an overview of what you should know.


Advertising

Update KB4103721 for Windows 10 V1803

I wrote about the cumulative update KB4103721 for Windows 10 V1803 in the blog post Windows 10 security updates May 8, 2018. This update includes a number of quality improvements, such as the problem that App-V scripts no longer work. Also the freezes observed with Cortana or Google Chrome should be fixed. According to this comment in my blog, this update also fixes the described problems with the Essentials Connector.

WSUS doesn’t offer this update

Within my German blog there are a couple of comments, reporting that WSUS doesn’t offer the Windows 10 updates of May 8, 2018. Especially the update KB4103721 for Windows 10 V1803 does not arrive in WSUS. In the US Technet forum there is this thread, dealing also with this topic. 

Black Screen bug and start issuese

In my German blog you can find this comment, which complains about a system that no longer starts. 

I have massive problems with KB4103721. 1803 was installed without problems. But after downloading KB4103721 my computer does not start anymore. Only the “spinner” can still be seen..

At Microsoft Answers forum is a discussion thread Windows 10 Cumulative Update KB4103721 Version 1803 where the thread starter warn about installing update KB4103721:

This update has some serious issues, specifically. Do NOT install this update after updating to Windows 10 version 1803. It will prevent your computer from booting up. I am stuck on the spinning circle for a long time. I have to use a Windows 10 USB to boot into the Troubleshooting and use Command Prompt to boot into safe mode. Please fix this update!

In the thread there are the usual postings of the kind ‘I run without problems’, but also a lot of confirmations. The thread now has 18 pages, so the problem seems to occupy a number of users. A German user writes:


Advertising

I have the same problem with the update on 3 computers at the same time.

One was recovered using a restore point. We are currently running an inplace upgrade with 1803 final version.

On the second computer only a reset to 1709 was possible. The new installation 1803 final version is currently running there.

On the third computer only the reset to 1709 was possible.

This isn’t all that great.

After all, the 3 computers were already running with 1803 pretty well. The update has destroyed everything again!

Users who installed Advanced System Care (ASC) could solve the problem by uninstalling ASC. But there are also those affected without ASCs. In this thread various (voodoo) fixes are suggested. At reddit.com there is this thread, where users are reporting a black screen:

The update is bricking my computer. After the update (KB4103721) download and installs, after restarting my computer will hang on a black screen and do nothing. The only way to fix it is to restore my PC to a previous restore point, where the PC will boot up normally again. Automatic Updates then installed the update again and the issue returned. After a restore point, my PC booted again

How do I get rid of the update?

The first solution to uninstall the update that blocks the boot process is this approach:

1. Try powering down the system three times, if it hangs in the boot process. 

2. Once Windows 10 displays Windows 10 PE mode with the repair options, try uninstalling the update.

The first method is to use System Restore and roll back. An alternative method is to select the safe mode at boot time. If Windows 10 then starts, you can uninstall the update in this mode. This page outlines the approach. 

Microsoft warns previously ahead of Intel SSDs

Microsoft has added within the kb article for update KB4103721 a known issue. There is a warning, that an upgrade to systems with Intel SSDs may causing issues:

When attempting to upgrade to the Window 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may repeatedly enter a UEFI screen after restart or stop working.

Microsoft is working with OEM partners on a fix and has suspended the feature update to Windows 10 April Update on these machines (see my article Windows 10 V1803: Rollout stopped for Intel SSDs).

Warning ‘Settings are managed’

Furthermore, the warning “Some settings are managed by your organization” appears in red font in the settings under Windows 10 April Update. In this (German) article, the registry entries for deactivation are mentioned. Start the command prompt with Run as administrator and execute the following command:

Reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection” /v “DoNotShowFeedbackNotifications” /t REG_DWORD /d “1” /f >nul 2>&1

This is one command (I broke it into two lines for formatting reasons). After executing the command, restart Windows. This also fixes the feedback frequency under Privacy. To undo this, the following command is required:

Reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection” /v “DoNotShowFeedbackNotifications” /t REG_DWORD /d “0” /f >nul 2>&1

Quite a few problems – Windows as a service – always something to do …

Similar articles:
Windows 10 security updates May 8, 2018
Windows 10 V1803: Rollout stopped for Intel SSDs
Windows 10 V1803 update creates a new OEM Partition
Windows 10 V1803 update creates a new OEM Partition


Advertising
This entry was posted in issue, Update, Windows and tagged , . Bookmark the permalink.

6 Responses to Windows 10 V1803: (Boot-) issues with update KB4103721

  1. Error says:

    “WSUS doesn’t offer this update”

    To solve that I have to install 2012R2 may update on wsus server and reboot, right after that KB4103721 was needed for 1803 clients.

  2. Paul says:

    Same happening on my PC ! After 1803 Feature update ! When booting after the post screen all you get is the BLACK screen of death and the small spinning timer ! After restoring the PC back to 1709 via system image, have disabled any feature updates in the advanced options for 364 days !
    Waiting for a Fix ! But how many people will have to suffer this !

  3. John Okane says:

    not just in Germany but also here in Philippines. I’ve had headaches now for 2 weeks. I’m using my old 5 year old laptop with Windows 7 as I’m frightened my new MSI laptop will be permanently broken.
    My sister in Australia also has same problem so it’s more widespread than Germany.

    regards,
    John

  4. Advertising

  5. Les Whitehouse says:

    Here in the UK, I had the same issue (black screen and spinning cursor). I used system restore to get into Windows, then turned off Windows update. Not an ideal workaround!
    My Windows Defender was also affected. It is turned off, and I can’t turn it back on, yet every file I try to download in Edge, IE or Chrome gets deleted with a message saying it was infected with a virus. This includes downloads from Microsoft, and I’m certain the warnings are a mistake. I’m worried about turning Windows update back on. What can we do? How will we know that a fix is issued (if it ever is)!?

  6. Since Windows made the updates “forced” with Windows 10, we couldnt get rid of issues. When
    i installed update 1803, i have encountered “boot loop” problem
    before and i could restored it back to previous update. Now i tried second time and i got same boot loop. I will turn back to 1709 and delay updates till next update. That was a very informative article. Thanks for all your effort.

  7. Yoshy262 says:

    I have the same problem with 1709 version.
    I’ve got in my company around 60 laptops with the same issue, the issue apears always after WSUS but I cannot find the culprit.
    KB4103721 is not installed in, still searching for a way out of this clusterf..k

Leave a Reply

Your email address will not be published. Required fields are marked *